for production mode, you stated just run "build" but I got errors in my server when I did that
See original GitHub issueI am also using Docker compose for production by the way. But I don’t think that matters.
What worked for me in production was I needed to run
sudo docker-compose -f production.yml run --rm django python manage.py tailwind install
Followed by
sudo docker-compose -f production.yml run --rm django python manage.py tailwind build
At least that’s true for the very first time.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
npm run build success but got an error when I run next start
I execute npm run build success but got an error message > Could not find a valid build in the '.next' directory! Try...
Read more >Identify and Fix Build and Deployment Errors in Your Angular ...
In this guide, you will learn how to spot some of the most common build and deployment errors and how to resolve them...
Read more >How to fix build failures with `create-react-app` in production
If your build is using create-react-app and has been failing since approximately the 18th of June 2020, this post will help you fix...
Read more >The command "npm run build -- --prod" exited with code 1 error
Try running: ng build "prod" and see what the actual error is.
Read more >Reactjs Build Production: Optimize Performance - CopyCat Blog
In this article, we will be taking a deep dive into the Reactjs build production, deployment, and tips on optimising your app's performance....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you Tim
Yes, generally it’s a good idea to commit package-lock.json, since it “freezes” your dependencies and you can be sure that you have same versions everywhere.