https://guides.derekleeds.cloud/tags/forgejo/Recent content in Forgejo on Derek's GuidesHugoenSat, 13 Jun 2026 13:38:27 -0500https://guides.derekleeds.cloud/docs/hermes/hermes-gitops-sre-assistant/Sat, 13 Jun 2026 00:00:00 +0000https://guides.derekleeds.cloud/docs/hermes/hermes-gitops-sre-assistant/<p>Hermes is most useful when it acts like an SRE assistant, not a magic production button. The workflow is simple: investigate, plan, change the source of truth, validate the result, and document what happened.</p> <p>That order matters.</p> <h2 id="operating-principles">Operating Principles</h2> <p>My homelab has a few rules for Hermes-driven work:</p> <ul> <li><strong>Forgejo is the source of truth</strong> for private infrastructure state.</li> <li><strong>GitHub is the source of truth</strong> for public guides like this site.</li> <li><strong>Komodo manages Docker Compose infrastructure and management-plane stacks.</strong></li> <li><strong>ArgoCD manages Kubernetes application workloads.</strong></li> <li><strong>Talos nodes are immutable.</strong> No SSH archaeology, no hand-edited snowflakes.</li> <li><strong>Secrets stay out of chat and docs.</strong> Use 1Password, environment references, or SOPS-encrypted files.</li> <li><strong>Documentation is part of the task.</strong> If it is not documented, it did not happen.</li> </ul> <p>Hermes can help with every part of that flow, but it does not get to invent a new source of truth because it found a convenient command.</p>