Deploying a side project shouldn't require a Kubernetes tutorial. Heroku is gone for hobby projects, and the remaining options either cost per-seat or hide the build. I wanted git push → live URL, with the logs visible while it happens.
A self-hosted PaaS:
deploy:queue)git clone → docker build from the repo's Dockerfile → docker run → generate an Nginx vhost for <subdomain>.<domain> → reloadlogs:<id>; the browser subscribes over SSE and renders the build log liveBuilds take minutes. Doing them inside the HTTP request means a dropped connection kills a deployment. Redis as both queue and pub/sub keeps the worker stateless and restartable.
One-way streaming with automatic reconnect and no extra protocol to maintain — the client is an EventSource and a <pre>.
Instead of an in-app proxy, each deployment gets a generated vhost. Routing stays fast, TLS is centralized, and the app never handles customer traffic.
Push a repo, watch the build stream, get a URL. Multi-project, per-deployment logs, retry and teardown included.
I understand the boring parts that make deploys work — process isolation, idempotent builds, log durability, reverse-proxy config — and I can build them from scratch.