erztemplerobba
Explore posts from serversStrapi database reset after re-deploy
Only had that problem with render.com and heroku free plans but that's how it's supposed to be cause their free tier goes to sleep after a while. Could it be the JWT session token that's getting thrown away after some time so you get 401 unauthorized? Strapi might have to re-auth after long periods of inactivity.
My Strapi wasn't up long enough to experience these kinds of problems, tho. Still struggling with non persistent data 😄
35 replies
Strapi database reset after re-deploy
Got it. Maybe it's just the free plan on heroku that wipes the db then. Thanks a lot for the info!
@Angelo Are you sure that Railway always sets up the Strapi build to reconfigure the db after each delopy? In that case, I know that I can stop tinkering to make it work 😄
35 replies
Strapi database reset after re-deploy
That's weird. I've been searching the web for this issue and found tons of people that have the same problem with heroku wiping the db. Are you maybe using an external postgres db for your heroku-hosted Strapi @thanneman ?
If it's true that Strapi wipes the db on each deploy, the whole thing is pretty much useless. They can't expect the user to always have exactly the same build running for years and years only to preserve data
35 replies
Strapi database reset after re-deploy
It does, unfortunately. It's a total fresh Strapi installation without any changes to config files or anything like that. I just entered the environment variables and watched railway install strapi.
So I wouldn't know how to fix that. I haven't found any configuration options on the railway dashboard.
35 replies