Strapi Deployment database wipes after every commit.

Anonymous

TRIALOP

2 years 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!

24 Replies

Anonymous

TRIALOP

2 years ago

N/A

brody

EMPLOYEE

2 years ago

are you running strapi in develop mode?

Anonymous

TRIALOP

2 years ago

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

brody

EMPLOYEE

2 years ago

may i ask why dont you wanna use the template?

Anonymous

TRIALOP

2 years ago

Anonymous

TRIALOP

2 years ago

i think i see why…

brody

EMPLOYEE

2 years ago

sqlite

Anonymous

TRIALOP

2 years ago

ahha

Anonymous

TRIALOP

2 years ago

fml

brody

EMPLOYEE

2 years ago

use template 🙂

Anonymous

TRIALOP

2 years 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

brody

EMPLOYEE

2 years ago

use node 20 then

Anonymous

TRIALOP

2 years ago

I have tried. it breaks deployment

brody

EMPLOYEE

2 years ago

try node 18 then