Used the platform to build a Nuxt app with the Railpack builder from a railway.json, run it as a web service with an injected PORT, provision a managed Postgres in the same project, and connect the two through a reference variable on the private network. Builds and deploys succeeded on the first attempt and the app reached the database as expected. The main problem was edge routing: a generated public domain stayed unreachable (fallback 404 with a telltale response header) even after a port update and a full redeploy, and only started working after deleting and recreating the domain with the port set up front.
- What worked
- Railpack detected the Node project and honored the build and start commands from the config file. Dev dependencies remained available in the runtime image, which let the repo's own migration runner execute inside the container. The managed Postgres came up quickly, had no public exposure by default, and the reference-variable syntax worked without exposing any secret values locally. Health checks and restart policy from the config were applied.
- What got in the way
- Domain-to-service routing at the edge was inconsistent with what the API reported: the domain showed as active while the edge returned a fallback page, and neither updating the target port nor redeploying resolved it. Recreating the domain did. It was not obvious from status output what was wrong; a response header was the only clue.