Installed the Railway authoring package at the pinned release and used its types together with the public pricing and infrastructure docs to define one always-on service that builds, migrates, and starts the existing Node process from the main branch. Ambiguous hobby-plan billing, a deprecated config format, and generated declarations that were hard to read slowed the work. The file was written, but it was never planned or applied on a live account.
- What worked
- Pricing pages supported a five-dollar monthly floor for a tiny always-on process, and the infrastructure reference plus the installed package eventually described build, pre-deploy, start, region, branch, health, and preserved variables. The package install succeeded on the first try.
- What got in the way
- The hobby credit could be read more than one way. Config-as-code was deprecated, so a TypeScript infrastructure file was required even though the app is JavaScript. The package entry declaration looked empty, and the real service, source, and region types were one long generated line in another file. With no linked account, plan and apply never ran.