2 years ago
As you may know, Railway is moving away from database plugins and moving towards database services:
The new way of creating databases has been GA for almost a month now and we've recently released docs on how to migrate your legacy plugins to a database with an attached volume:
On January 31, 2024 all legacy plugins will be inaccessible on Railway.
We would like to help make your migration as seamless as possible. This thread is to discuss any and all things related to the migration.
Please let us know about any issues you encounter. We're here to help and with your input we can improve the process for all.
3 Replies
2 years ago
I recently migrated our single Redis plugin over to a new Redis Database service. I used the 1-Click migration.
I've had a couple issues I ran into that I thought I might link here as well in case others encounter similar things:
Unlinked preview environment variables (see Discord thread here: https://discord.com/channels/713503345364697088/1176706932778749992/1176706932778749992)
Re-deploying Redis docker containers (see Discord thread here: https://discord.com/channels/713503345364697088/1176656164675661834/1176656164675661834)
Things are up and running now though, I appreciated the 1 click flow since I didn't quite grasp all the changes immediately.
2 years ago
We hit the one click migration button too, and the postgresql database migration went fine, but strapi had some docker related deployment errors, and now we can't even access the project, since it gives us a 404 error.
2 years ago
We hit the one click migration button too, and the postgresql database migration went fine, but strapi had some docker related deployment errors, and now we can't even access the project, since it gives us a 404 error.
This was a separate issue on the dashboard which should be fixed now.
2 years ago
Completed!
Status changed to Completed jr • almost 2 years ago