That said, I submitted a PR into the railway CLI repo adding the backup command https://github.com/railwayapp/cli/pull/678(I am not a Rust coder so the PR likely requires improvements, but if eventually merged could be a nice shortcut for making database dumps)

@kllymx The simplest way would be to:Ensure that your Postgres database is reachable over public network (it is by default). If it's not - go to the settings and ensure that under Public Networking you have a generated domain set. If not - just click Generate Domain and apply the change.Go to the Postgres service Database tab and click "Connect" at the right top. Find connection string at the Public Network tabOnce you get the connection string that includes the username, the password, database name and the URL of your Postgres instance (the connection string looks likepostgresql://<username>:<password>@centerbeam.proxy.rlwy.net:49084/<database_name>) and the default database name is usually railwayYou can then use any client to make a dump of your database ( i.e. pgAdmin https://www.postgresql.org/download/ , HeidiSQL https://www.heidisql.com/ or similar ) by connecting to your database and dumping it into an SQL file that you can later upload the same way to another database instanceHere is the simplest way of making a dump using pg_dump CLI (that you'll get by installing pgAdmin):pg_dump "<CONNECTION_STRING_HERE>" -F p -f /path/where/to/save/dump.sqlp.s. if you're on Mac the simplest way to get the pg_dump utility is via Brewbrew install libpq that installs it into /opt/homebrew/opt/libpq/bin/pg_dump and on Linux even simpler by sudo apt install postgresql-client

In case you are still exploring options, I created this template with a migration tool.https://railway.com/deploy/postgres-migrator?referralCode=crisogYou should use it with caution anyway and make sure you have backups before using it.Depending on how technical you are, it might be safer than trying to do all of it manually.

Oh this is great, will try it out. Thank you!

@kllymx The simplest way would be to:Ensure that your Postgres database is reachable over public network (it is by default). If it's not - go to the settings and ensure that under Public Networking you have a generated domain set. If not - just click Generate Domain and apply the change.Go to the Postgres service Database tab and click "Connect" at the right top. Find connection string at the Public Network tabOnce you get the connection string that includes the username, the password, database name and the URL of your Postgres instance (the connection string looks likepostgresql://<username>:<password>@centerbeam.proxy.rlwy.net:49084/<database_name>) and the default database name is usually railwayYou can then use any client to make a dump of your database ( i.e. pgAdmin https://www.postgresql.org/download/ , HeidiSQL https://www.heidisql.com/ or similar ) by connecting to your database and dumping it into an SQL file that you can later upload the same way to another database instanceHere is the simplest way of making a dump using pg_dump CLI (that you'll get by installing pgAdmin):pg_dump "<CONNECTION_STRING_HERE>" -F p -f /path/where/to/save/dump.sqlp.s. if you're on Mac the simplest way to get the pg_dump utility is via Brewbrew install libpq that installs it into /opt/homebrew/opt/libpq/bin/pg_dump and on Linux even simpler by sudo apt install postgresql-client

Hey, I just want to let you know that I have deleted your message due to the incorrect information given.A database service should have a TCP proxy. Your instructions were on how to add an HTTP domain, and that simply will not work, as Postgres operates on TCP.