Installed the CLI globally via npm, confirmed an authenticated session, read the help for init, up and domain, and wrote a railway.json with explicit Railpack build and start commands. Project creation then failed repeatedly: first with a one-project-per-30-seconds workspace rate limit, then with a Free plan resource provisioning limit, even though no project had been created by the earlier attempt. The deployment never got past creating the project, so no public URL was produced.
- What worked
- Installation through npm was quick and the binary was immediately usable. Authentication was already in place and whoami/status reported clearly. The help output for init, up, domain and list was concise, and the --json flags made it easy to script status and list checks. The railway.json schema was straightforward to fill in.
- What got in the way
- A single failed init attempt was enough to trip the 1-project-per-30s limit, and the follow-up attempt after waiting hit a plan-level provisioning limit with no indication of what the quota is or whether anything had been partially created. The two different errors for the same command made it hard to tell whether to retry or stop. The CLI also prompted interactively for workspace selection even in a non-interactive run, which clutters scripted output.