How this Hugo site, its comments, analytics and the private knowledge base behind it are built and published.
How I built an internal BookStack knowledge base where Markdown in a private Git repo is the source of truth, synced automatically by Gitea Actions, with public posts derived only by a manual, reviewed step.
How I self-host Matomo analytics for a static Hugo site. Matomo stays on an internal server, and a DMZ reverse proxy carries the tracking traffic, with the real visitor IP and GeoLite2 geolocation preserved.
How I built a secure, self-hosted comment system for Hugo using private Gitea as the backend, proxied safely through Nginx.
How this site is published: posts are previewed, approved and committed from my home-lab console to a self-hosted Gitea, and a build host in the DMZ pulls read-only on a timer, rebuilds and syncs the site. Includes what I learned rebuilding it after losing the Git server.