Strapi Deployment database wipes after every commit.
GM, i have just recently started using railway for my strapi backend and db. I have followed some online guides and found that after committing a change, the data from the db is erased. I have read all the posts in the help channel that relate to this, but i cant seem to pinpoint the reason.
I have then gone and cloned the strapi template railway has and that does not seem to wipe the data after every commit. I wanted to compare my deployment against that to see the differences, but I could not find anything. Not sure if i need to make a help post or if someone has a link to a post I have missed.
Can someone help me understand what is going on here, so i can create a new strapi backend and db (not the template) where it does not reset after every commit.
Thanks!
22 Replies
Project ID:
N/AN/A
are you running strapi in develop mode?
nope. just went through and checked all the deployment logs, they all run in production
may i ask why dont you wanna use the template?
i think i see why...
Solution
sqlite
ahha
fml
use template π
I have spent 2 weekends configuring package versions because dependencies break. I am using nodejs 18, and i know the template is on 20, I am worried i will lose another 2 weekend :kek:
use node 20 then
I have tried. it breaks deployment
try node 18 then
Template doenst build in 18?
not sure i didnt try it in 18 tbh, it asked me for 20