Trying to deploy Strapi project it fails. It's the same build that works 4 days ago.
Hi I'm trying to deploy a strapi project but it fails. I try to redeploy the same project that builds correctly 4 days ago. But also fails so I think there's something wrong on the CI Here's the build log. Hope it helps
Thanks
29 Replies
Project ID:
6eac7725-1303-464a-a12e-c54b827c5d96
I have my project waiting please, need some help on this
send me your railway.json file, if you don't have a physical file in your project send me the auto generated one that can be found in the details tab of your latest deployment (even a failed deployment has one)
I didn't found the autogenerated json here i found the deployment id
On three dots options I only have redeploy or remove
I need the railway.json file
I'm just a community member, I can't do anything with the id's
I didn't find railway.json file in my failure deploy options
okay let me know when you find it
4 days ago the same build works fine
and now I have errors on the building step
^
send your package.json please
any reason you are starting strapi in development mode? development mode is meant to only be ran locally
I try develop and regular script both fail
do you have a repo for this
Yes
But it’s private
add me? there shouldnt be anything private afaik
I create the project from railway Strapi template
i just dont understand why python is required all of a sudden
GitHub
GitHub - railwayapp-templates/strapi: Deploy Strapi on Railway. Nex...
Deploy Strapi on Railway. Next-gen headless CMS. Contribute to railwayapp-templates/strapi development by creating an account on GitHub.
but hey, if it wants python, lets give it python lol
Me neither
i will give it python, hold please
Is there an option to open a ticket?
hold please
use this railway.json file (put it in your project folder) and this will tell railway you want python too
Ok thanks I’ll try it later
deploying .... lets see if it works
Looks like sqlite package was the problem, not sure why. I need this package to work in local without production database
yeah I figured that's why you had sqlite, maybe try moving sqlite to the dev dependencies? and always regen your lock file!
any idea how I can regen lock file always when I deploy ¿
run
npm i --package-lock-only
locally