Gagarin vs Railway says where Railway is the better

pick. Read that first if you have not decided. This post is for the afternoon

after you have: what you type, in what order, and where you lose time.

The project is a common shape. A web service, a worker that reads the same

database, a Postgres with a few gigabytes in it, and a cron job that runs a

report at three in the morning. Each service has a Dockerfile, because Railway

builds from one when it finds one. If yours build with Nixpacks or Railpack,

budget an hour at the start to write two Dockerfiles. Nothing else here depends

on the shape of your code.

The clock below is a budget for a project this size. Yours will differ by the

size of the dump and the state of your DNS.

13:00: Write down what only Railway knows

Three things live on Railway and not in your repository: the environment

variables, the database, and the schedule.…