Deploying a public OpenWiki viewer through Argo CD and generic DNS publishing
I added the necessary files and scripts to publish the OpenWiki site publicly via Argo CD and to make the DNS publishing workflow work for any site, not just Mastodon.
Introducing the public wiki viewer deployment
I created clusters/homelab/apps/openwiki/nginx.conf and clusters/homelab/apps/openwiki/service.yaml to expose the OpenWiki service on port 8080 with the required headers and location rules. I added a “Public viewer” section to openwiki/operations/wiki-maintenance.md describing how Argo CD rolls the deployment when the generated ConfigMap changes, and how to use Cloudflare Tunnel to forward the hostname. I also added a new script scripts/export-openwiki-site.py that exports wiki pages, visualizes them, and produces a ConfigMap for Argo CD.
Generalizing the DNS publishing workflow
I modified .github/workflows/mastodon-public-dns.yml to accept a site input and renamed the job to “Publish Reviewed Tunnel DNS”, adding environment variables so the same workflow can publish DNS for mastodon or openwiki. I updated scripts/mastodon-public-dns.py to take a site argument, changed the ready function to include the site in the apps list, and adjusted the reconcile call accordingly. The test file scripts/ci/mastodon-public-dns-test.py was altered to parameterize the desired record and to call dns.reconcile with the site, and scripts/ci/network-policy-peers-test.py was updated to verify that the openwiki peer is allowed through the network policy.
Verification steps and next checks
After merging, I will verify that the public viewer is reachable through the Cloudflare Tunnel, that the DNS CNAME record for openwiki resolves correctly, and that the CI pipeline passes the updated tests. The next concrete check is to run the workflow with site=openwiki and confirm that both openwiki and octelium-public appear as Synced and Healthy before dispatching the DNS update.
Platform engineering takeaways
Treating the public viewer as a first‑class Argo CD application with its own Service and nginx configuration creates a reusable pattern for any public service in the homelab. By parameterizing the DNS workflow and updating the related tests, the same pipeline can be applied to future sites without additional custom scripts. This reduces duplication and makes operational checks consistent across the cluster.