#Strapi Deployment database wipes after every commit.

26 messages · Page 1 of 1 (latest)

uneven latch
#

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!

crystal inletBOT
#

Project ID: N/A

uneven latch
#

N/A

glacial fiber
#

are you running strapi in develop mode?

uneven latch
#

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

glacial fiber
#

may i ask why dont you wanna use the template?

uneven latch
#

i think i see why...

glacial fiber
#

sqlite

uneven latch
#

ahha

#

fml

glacial fiber
#

use template 🙂

uneven latch
glacial fiber
#

use node 20 then

uneven latch
#

I have tried. it breaks deployment

glacial fiber
#

try node 18 then

uneven latch
#

Template doenst build in 18?

#

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

glacial fiber
#

change it

uneven latch
#

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

uneven latch
glacial fiber
#

sqlite is the default

uneven latch
#

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

glacial fiber
#

sounds about right

uneven latch
glacial fiber
#

no problem!