Strapi Deployment database wipes after every commit.

AnonymousTRIAL

a year ago

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!

0 Replies

AnonymousTRIAL

a year ago

N/A


a year ago

are you running strapi in develop mode?


AnonymousTRIAL

a year ago

nope. just went through and checked all the deployment logs, they all run in production


a year ago

may i ask why dont you wanna use the template?


AnonymousTRIAL

a year ago


AnonymousTRIAL

a year ago

i think i see why…


a year ago

sqlite


AnonymousTRIAL

a year ago

ahha


AnonymousTRIAL

a year ago

fml


a year ago

use template 🙂


AnonymousTRIAL

a year ago

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


a year ago

use node 20 then


AnonymousTRIAL

a year ago

I have tried. it breaks deployment


a year ago

try node 18 then


AnonymousTRIAL

a year ago

Template doenst build in 18?


AnonymousTRIAL

a year ago

not sure i didnt try it in 18 tbh, it asked me for 20


a year ago

change it


AnonymousTRIAL

a year ago

Alright i will get onto it. Thanks for that mate!


AnonymousTRIAL

a year ago

cant believe this tho lol


a year ago

sqlite is the default


AnonymousTRIAL

a year ago

yeah must be referring to my database.js in the dev env


a year ago

sounds about right


AnonymousTRIAL

a year ago

That was it. Fixed up my database config files for production and all g. TY


a year ago

no problem!