From code change
to running server.
Two triggers. Three artifacts. A server in the organiser’s own cloud account.
Two triggers, two jobs
Free runners for public repositories. Checks and builds run on GitHub’s machines, never on our own server.
One tag, three artifacts
No cgo, no emulation. Both architectures cross-compile on one runner.
From tag to their server
One manual step: copy the provider’s API token. The organiser never opens a terminal.
Teardown uses the same skill and deletes the server.
What is inside the box
One shared mount keeps the app out of the content path. Simple Host writes sites; Caddy reads it directly.
Internal ports stay internal. Only Caddy publishes ports; 8090 and 5432 are never published. These are Docker named volumes; the Kubernetes equivalent is a persistent volume claim.
Two domains, on purpose
No domain? An organiser could be given a subdomain of a domain the project controls.