Overview
Git deployments is part of the Better-PaaS workflow for turning a VPS into a practical app platform. It reduces manual server work while keeping infrastructure, runtime data, and credentials under your control.
What it does
Deploy from Git repositories and rebuild from a branch when code changes.
Why it matters
Small teams often lose time on repeated server tasks: editing proxy configs, watching logs over SSH, managing env vars, and recovering from bad deploys. Git deployments gives that workflow a predictable place in the dashboard.
How to use it well
Keep the setup simple, test with a small app first, and verify the operational path before relying on it for production workloads.
- Start with one app
- Check logs after each deployment
- Document environment variables
- Create backups for stateful services
Operator tip
Connect GitHub with a token scoped to required repos only. Enable webhooks after the first manual deploy succeeds.
FAQ
Does Git deployments require Kubernetes?
No. Better-PaaS is designed around Docker containers, Caddy routing, and a lightweight Go control plane.
Is Git deployments available for every app?
Most features apply broadly, but stateful apps, custom Docker images, and unusual networking setups may need extra configuration.