Push to main and watch your app build, test, and deploy to your server automatically and safely.
Cloud & DevOpsPDF · 7 pages· v1.0
4.2A practical guide to wiring up continuous deployment so that pushing to your main branch automatically builds, tests, and deploys your application to a VPS — securely, using GitHub Actions. This is for developers who are tired of SSHing in to deploy by hand and want a reliable pipeline without adopting a heavy platform. You'll build a workflow that runs your tests, builds and pushes a Docker image to the GitHub Container Registry, and then connects to your server over SSH to pull and restart the app. The security model is front and centre: a dedicated deploy user with a restricted key, secrets stored in GitHub, and no credentials ever printed in logs. The guide covers the parts that trip people up: setting up the SSH key and known_hosts correctly so the deploy step doesn't hang or fail, authenticating to the container registry, making the deploy idempotent, and adding a manual approval gate for production if you want one. It finishes with rollback and how to debug a failed run. After this guide, every merge to main can ship to your server on its own, with tests as a gate, and you'll understand the pipeline well enough to extend it.
No. GitHub Actions includes a generous free tier for most projects, and this runs entirely within it.
Yes, when done right. The guide uses a dedicated deploy user, a key stored as a secret, and pinned known_hosts so there's no trust-on-first-use risk.
Yes. The guide shows GitHub Environments with a required reviewer so production waits for a human click.
Because images are tagged per commit, you re-run the deploy step pinned to the previous tag. The guide covers it.
Read the full refund policy and trust & safety terms.