prosody

7 Commits

Author	SHA1	Message	Date
jason	a96d3b031e	📝 repo cleanup 📝 CI / Build image (push) Failing after 14m34s Details CLAUDE.md	2026-07-30 22:35:25 -04:00
jason	c2538cdc06	📝 Migrate /var/lib/srv docker paths to /srv in README 📝 CI / Build image (push) Has been cancelled Details Update volume mount examples and dockerHome variable from the old /var/lib/srv/$USER/docker layout to /srv/$USER/docker. - README.md: update volume path references to /srv/$USER/docker README.md	2026-07-10 12:18:11 -04:00
jason	4950a72df2	🐛 Fix resolv.conf: add search . and ndots:0 to block domain search 🐛 --domainname on the container sets the kernel domainname, which c-ares uses to infer a search domain even when /etc/resolv.conf has no search line. This caused c-ares to query github.com.casjay.work AAAA and get the host's own IPv6 address, routing all outbound HTTPS to the local nginx instead of the real server. Adding 'search .' and 'options ndots:0' explicitly disables search domain inference regardless of the kernel domainname setting. - rootfs/usr/local/etc/resolv.conf: add search . and options ndots:0 rootfs/usr/local/etc/resolv.conf	2026-06-05 14:34:33 -04:00
jason	64de0a8959	🐛 Fix container DNS: ship resolv.conf without search domain 🐛 Hosts with a search domain cause containers to inherit it. When the zone has a wildcard AAAA record, public hostnames resolve to the host's own IPv6 address instead of the real server, breaking all outbound HTTPS and DNS from inside the container. The entrypoint already has a hook: if /usr/local/etc/resolv.conf exists it replaces /etc/resolv.conf at container startup. Ship a clean resolv.conf with Cloudflare + Google DNS and no search domain so container DNS is always correct regardless of host configuration. - rootfs/usr/local/etc/resolv.conf: new file — clean DNS, no search domain rootfs/	2026-06-05 12:44:39 -04:00
jason	6193044e65	📝 Update prosody README with install instructions 📝 - README.md: add automatic install/update instructions and dockermgr usage README.md	2026-06-04 14:34:50 -04:00
jason	d61cc57672	🔧 Fix stale GitHub Actions SHAs 🔧 All pinned action SHAs were outdated; GitHub couldn't resolve them, causing both CI and Release workflows to fail at job setup. - .github/workflows/ci.yml: update actions/checkout → v6.0.2, docker/setup-buildx-action → v4.0.0, docker/login-action → v4.1.0, docker/metadata-action → v6.0.0, docker/build-push-action → v7.1.0 - .github/workflows/release.yml: same action updates plus softprops/action-gh-release → v3.0.0 .github/workflows/ci.yml .github/workflows/release.yml	2026-05-19 13:05:51 -04:00
jason	dfd79d5774	🦈🏠🐜❗ Initial Commit ❗🐜🦈🏠	2026-05-19 12:54:07 -04:00