Production database practices
debashisbiswas
PROOP

2 years ago

I'm currently running a MySQL database in production. Here's what I'm curious about:

  • It's not great to leave the database open to the public internet. The TCP proxy is convenient, but is it recommended to disable it in production?

  • If the TCP proxy is disabled, what's the best way to restore from backups? I'm currently working on setting up a cron job to back the database up to S3, but I'm not sure what the restore process would look like. If I'd need to restore by connecting from local, I would need it to be exposed to the public internet somehow, correct? Maybe need a jumpbox or something similar?

8 Replies

debashisbiswas
PROOP

2 years ago

N/A


2 years ago

  1. correct, it's not great and for that reason all my templates come without the tcp proxy on the databases.

  2. you could spin up a ubuntu ttyd image in the same project with the required cli tools to download and restore the backup.


debashisbiswas
PROOP

2 years ago

I like that option better


debashisbiswas
PROOP

2 years ago

How would you connect to that? Railway CLI?


2 years ago

though the web browser


debashisbiswas
PROOP

2 years ago

oh I see what you mean, web browser to connect to ttyd, not the railway web app


2 years ago

correct


debashisbiswas
PROOP

2 years ago

Interesting, okay. It'd be nice to see better management tools in the future, but this should work for now


Loading...