13 days ago
I accidentally deployed a GitHub commit that replaced my production /app/shine.db. The production database contained important orders through August 8, 2026.
The affected previous Railway deployment is:
64994d49-aaca-40c3-aa77-e4f0e0da8111
The current deployment has /app/shine.db, but it only contains 74 orders through June 6, 2026. The local Git repository is not a current copy of the production database.
The previous deployment has no Volume attached. I need to know whether Railway can recover or provide access to the filesystem/database from the previous deployment, specifically the /app/shine.db that existed before the new deployment.
Please advise on the safest recovery method. I do NOT want to rollback or overwrite the current deployment until the database has been recovered.
1 Replies
13 days ago
The service that hosts your shine.db has no volume attached, so the database was stored on the container's ephemeral filesystem. Ephemeral storage is discarded on every new deployment, which means the previous deployment's copy of /app/shine.db no longer exists and cannot be recovered. Going forward, attaching a volume to this service will persist your database file across deployments.
Status changed to Awaiting User Response Railway • 13 days ago
6 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 6 days ago