Skip to main content

H2. VPS path

What this page helps you do​

Launch on a VPS in a way that stays understandable after the first deploy.

Why it matters​

A VPS can be flexible and affordable, but it also hands you more responsibility. If you choose this path, you need a basic plan for updates, restarts, logs, HTTPS, and backups.

You should already have​

  • an app that runs locally
  • comfort with following server setup steps carefully
  • a reason to choose a VPS instead of managed hosting

Skip this page if​

  • you want the simpler default

Then go to H3. Managed hosting path.

What to do​

  1. Start with a clean server.
  2. Lock down basic server access in H5. Prepare your server.
  3. Put the app on the server using a repeatable deploy method.
  4. Add a process manager or equivalent so the app restarts if it crashes.
  5. Put a domain and HTTPS in front of it with D2. Set up Cloudflare and D4. HTTPS and SSL.
  6. Add backups, logs, and rollback planning before launch.

Things you need to know on a VPS:

  • where the app files live
  • how the app starts
  • how the app restarts
  • where logs go
  • who can log in to the server

Keep the VPS setup boring.

  • one app per server or a clearly documented platform layer
  • one clear deploy path
  • one place to check logs
  • one rollback method you understand

Common mistakes​

  • installing random packages until the app “works”
  • making manual hotfixes on the server with no record
  • having no restart strategy after a reboot
  • forgetting backups because the server itself feels like the backup

Next step​

Go to H5. Prepare your server and then H6. Deploy your app.

Advanced notes​

If you want a middle ground, consider H4. Self-hosted platform path, where a platform helps manage some of the server work for you.