8 months ago
Hi team,
at deployment: f517d418-1a55-4a4b-b582-d61f18712b75.
my data was lost even I have attached the volume there. Please assist me.
Thank you.
Pinned Solution
7 months ago
Thanks, I figured it out after couple try. In Railway, if we use NixPack and application is deployed with Docker, we need to mount sqlite file in /app/db/*.sqlite file.
4 Replies
8 months ago
Our team is working on getting back to you as soon as possible. In the meantime, we've found the following might help you get unlocked faster:
If you find the answer from one of these, please let us know by solving the thread! Otherwise, we’ll be in touch.
8 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 8 months ago
8 months ago
Can you provide more information? Where does your application expects the sqlite database and which mount path did you configure for your volume?
A common problem is that people mount volumes to the wrong path, so your application creates a database in the ephemeral container which is lost on a deployment.
8 months ago
SQLite just reads and writes to a file, you’ll need to make sure that file is saved inside the attached volume. If it’s stored anywhere else, like the default project folder, it won’t stick around between deploys.
7 months ago
Thanks, I figured it out after couple try. In Railway, if we use NixPack and application is deployed with Docker, we need to mount sqlite file in /app/db/*.sqlite file.
Status changed to Solved brody • 7 months ago