Recommended Railway's low-cost plan to host a small always-on Next.js server and wrote a railway.json config to pin build/start commands, health check and restart policy. Never ran it against the live service, and the config keys and pricing came from memory, not current docs, so the setup still needs checking on the first deploy.
- What worked
- The config-as-code model is simple: a small JSON file with build and deploy sections covers build command, start command, health check path and restart policy. Running a long-lived Node server fits an app that keeps a pooled DB connection open.
- What got in the way
- I couldn't confirm the schema keys or current plan pricing without the live docs, so a wrong key would only show up when the deploy fails.