spree_starter
spree_starter copied to clipboard
spree
Please guide to run a production build for the same
The documentation is missing crucial components on how to setup a production server. Can you please incorporate it in the documentation? For now, can someone guide me how to setup a production build using the same system.
I couldn't even setup my local server in my Macbook with M1 chip. https://github.com/spree/spree_starter/issues/968
were you able to setup locally?
Yes I was able to set it up locally. @linktoming
thanks, by way of docker (didn't work for me) or adding it to an existing rails app (worked for me as well)?
@argoyal this repo is pre-configured to run flawlessly on Heroku - I would recommend reading https://dev-docs.spreecommerce.org/deployment/heroku and https://devcenter.heroku.com/articles/getting-started-with-rails6
@argoyal Please check setup-without-docker branch. You can just follow any rails production deployment guidelines.
@argoyal Please check setup-without-docker branch. You can just follow any rails production deployment guidelines.
This branch does not exist @moonstruck
@argoyal this repo is pre-configured to run flawlessly on Heroku - I would recommend reading https://dev-docs.spreecommerce.org/deployment/heroku and https://devcenter.heroku.com/articles/getting-started-with-rails6
Sure thing @damianlegawiec.
@damianlegawiec I think it would be good if we get this documented would help a lot of people.
@argoyal Please check setup-without-docker branch. You can just follow any rails production deployment guidelines.
This branch does not exist @moonstruck
This has been merged into main branch. Commit
I am receiving the following error log (attached the log file) when I am trying to run this setup as a production build. Can you please help me understand where I might be going wrong because my team has been scratching their head over this. error_log.txt
@damianlegawiec @moonstruck
@msshahanshah figured out a fix for this. apparently it was due to a missing gem which is a required dependency for production builds. Mustafa, you can share details, if I did not cover the entire context.
@msshahanshah figured out a fix for this. apparently it was due to a missing gem which is a required dependency for production builds. Mustafa, you can share details, if I did not cover the entire context.
It would be great to share that information with others
It would be great if this was documented for anyone self hosting the application.
Hi, I have same problem with production and as I see production is only configured for heroku, could you please help to make it for standalone ?
