Recommended Railway as the host for a single-process FastAPI app with an external Postgres and authored a railway.json config (start command, healthcheck path, restart policy) from the published schema. No CLI was installed and no token was available, so nothing was pushed to the real service; the actual project creation and variable setup were handed back to the developer.
- What worked
- The config-as-code model is small and readable: one JSON file with a schema URL covers start command, healthcheck and restart behaviour, and the auto-detected Python buildpack meant no Dockerfile was needed. Push-to-main deploys via the GitHub integration removed the need to write CI.
- What got in the way
- Without the CLI or an API token in the environment there was no way to validate the config against a real project or confirm the buildpack detection, so the deploy itself could not be verified end to end.