Secure VPS Deploy
This is the kit's first-party VPS deployment skill.
Use it when the chosen deployment path is VPS. Do not use it for normal Vercel deployments.
What This Skill Does
It compresses the VPS path into one opinionated workflow:
- local preflight
- SSH bootstrap
- server hardening
- firewall policy
- edge proxy setup
- app rollout
- verification and rollback
This skill is the index.
Detailed guidance lives in references/.
Utility helpers live in scripts/.
When to Use
- The user explicitly wants a VPS.
- The product must be self-hosted.
- SSH, Nginx, firewall, or direct server control is required.
- Docker is part of a VPS rollout.
Core Rules
- SSH access and rollback come before hardening.
- Never close the only working connection before the next one is verified.
- Open only the ports the deployed system actually needs.
- Reverse proxy setup is explicit; do not assume Nginx is required if it is not.
- Credentials and access are still collected through
/setup, one surface at a time. - Verification is mandatory after every major phase.
Standard Workflow
- Run
scripts/vps-preflight.sh - Read
references/01-local-preflight.md - Read
references/02-ssh-bootstrap.md - Read
references/03-server-hardening.md - Read
references/04-firewall-policy.md - If a reverse proxy is needed, use
references/05-nginx-edge.md - If the app is containerized, use
references/06-docker-rollout.md - Finish with
references/07-verification-and-rollback.md
Scripts
scripts/vps-preflight.sh— checks local tooling before a VPS rolloutscripts/render-nginx-site.sh— prints a starter Nginx site config from a domain and upstream
References
references/01-local-preflight.mdreferences/02-ssh-bootstrap.mdreferences/03-server-hardening.mdreferences/04-firewall-policy.mdreferences/05-nginx-edge.mdreferences/06-docker-rollout.mdreferences/07-verification-and-rollback.md
Source Notes
This first-party skill is distilled from the imported ssh, secure-vps-setup,
ssh-hardening, firewall-configuration, nginx-configuration, and
docker-deployment skills. Use those as deeper fallbacks only when the narrower
implementation details are needed.