Infrastructure I run, websites I've shipped, and a few games and tools in progress.
One host · four repos · zero manual steps
Four Go services live behind one SSH port on a single EC2 instance. Merging to main builds the image, ships it, and restarts the service on the host itself — and every save is streamed to S3 so the instance underneath is replaceable.
$ git push origin main
Commit
main deploys for real.
Test
ubuntu-latest
Runs again on release. Never skipped.
Publish
ubuntu-latest
Auth is the run's own token. Nothing stored.
Deploy
[self-hosted, production]
Runs on the box, not over SSH.
Live
Prober confirms the new version.
Why the runner lives on the host
The host's real sshd is locked to a single IP, and GitHub-hosted runners come from an ever-changing range that will never match it — a dial-in deploy job would just time out. Registering the runner as a service on the box instead means the deploy reaches production without anything having to be let in.
Durability
The volume is a cache; the bucket is the fleet's data. Credentials come from the EC2 instance role, so no AWS key exists in any image or compose file. Drilled locally against MinIO — a hard kill plus a volume delete restored clean, with a measured 12s RPO against an enforced 60s budget.
Those drills prove the mechanism. Only the live host proves the credentials — an instance-loss drill is still on the list.
Topology
A home for my film and digital photography.
A marketing site for a small-business IT provider.
A website for an independent IT advisory firm in Athens, Georgia.
A website for a CPA firm handling complex individual and small-business taxes.
Small games and tools I build for the browser.
