Closed katopz closed 8 years ago
Try to use docker-compose stop
instead of docker-compose down
.
I did try docker-compose stop
but it still happen when docker-compose up -d
and docker-compose restart
after that.
I created a docker-compose-production.yml for parse-dashboard production for you:
PARSE_DASHBOARD_ALLOW_INSECURE_HTTP=1 USER1=user1 USER1_PASSWORD=user1 MASTER_KEY=myMasterKey APP_ID=myAppId docker-compose -f docker-compose-production.yml up
ref. https://github.com/yongjhih/docker-parse-server/commit/dc42e684d6b08933b36b9917a1531ba722507464
Cool! I'll try
Refer to https://docs.docker.com/compose/production/
This configuration file only needs to include the changes you’d like to make from the original Compose file.
I think it should contain only different between dev
and prod
there not just copy & paste.
We should do something like this https://docs.docker.com/compose/extends/#different-environments
No rush on this btw, You can leave this to me. I'll made a PR when I'm done with it. :)
Cheers
Is it expected behavior?
Refer to
webpack --config webpack/build.config.js --progress --watch
And after startlocalhost
I need to wait 40621ms for the build every time I restart even nothing changed. It's look like config for development for me, Is there any config for production environment there?Thanks