DevOps
Pick where this project should run, then follow the setup for that path.
Deploy path
Code is built in CI, shipped as an image or a platform build, run on a platform or a VPS, and then watched.
- Code
- Build
- Ship
- Run
- Operate
"PaaS, edge" is the detail under Platforms. Monitoring is the ELK notes; a single VPS also runs a status page reached only through an SSH tunnel, covered in the VPS playbook.
Where should this run?
The same choice, with the trade-offs written out, is the platform decision chart. Prices and free-tier limits on those pages were checked on 2026-11-01.
Moving between options
A frontend can stay on Vercel, Netlify or Cloudflare Pages while the APIs move. The move that these notes record is that shape: two API backends, each with a production and a staging instance, left a PaaS and landed on one VPS, with one Postgres instance (one database and one role per app) behind a reverse proxy. The frontends stayed on a platform. The checklist, from an empty server through DNS cutover, is Self-host a Docker stack.
Connects to
- Deployment platforms: the comparison, grouped by service, and one page per platform.
- Self-host a Docker stack: the VPS playbook.
- CI/CD: build the image, push it, deploy over SSH, roll back.
- Cloud computing: when the next step is a cloud building block instead of a single server.