Guide shows how to move a web service, worker and Postgres database from Railway to Gagarin

The article walks through migrating a common setup of a web service, a background worker and a database off Railway and onto Gagarin in an afternoon. It explains how to export environment variables and sort out which ones belong to Railway, the database, external secrets, or individual services. The database is moved by dumping it with pg_dump and restoring it through a tunnel opened with gg connect. Secrets such as Stripe and SMTP keys are stored as external resources, and services are deployed with gg ship along with explicit dependency declarations. The piece also covers rotation, rollback and replacing Railway's push-triggered builds with CI-driven deploys.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in