This repository has been archived by the owner on Aug 30, 2021. It is now read-only.
MEAN.JS can't set to run in 'PRODUCTION' mode inside Docker #1431
Comments
3 tasks
FedeG
pushed a commit
to FedeG/mean
that referenced
this issue
Aug 20, 2016
Add Dockerfile for production Fixes meanjs#1431 Fixes meanjs#1435
lirantal
pushed a commit
that referenced
this issue
Aug 25, 2016
Add dockerfile and compose for production (#1438) Add Dockerfile for production Fixes #1431 Fixes #1435 * feat(deploy): Add docker-compose.yml for production Add docker-compose.yml for production Fixes #1435 * feat(deploy): Update documentation for deployment Update documentation for production deployment Fixes #1435
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Changed the ENV NODE_ENV to production in the Docker file, before building the image.
Also tried running container with docker run -e "NODE_ENV=production"-i -t --name www1
Nothing seems to make the MEAN.JS app run in production mode except for grunt prod, which I am not exactly sure how it can be configured to run in the docker container.
Verified that the NODE_ENV is in fact set to production via: docker exec -it www1 bash printenv command.
The text was updated successfully, but these errors were encountered: