Closed blackmouse572 closed 8 months ago
I would setup .env.examples and pull these into docker-compose instead of hard coding.
Usually I've only used docker-compose locally in dev to setup the supporting services such as redis,postgresql,nginx etc. It might be that someone just wants these supporting services without building the local Dockerfiles. Two compose files might be useful depending how prod is deployed..
Popping a docker-compose up/down script in the package.json might be useful
Usually I've only used docker-compose locally in dev to setup the supporting services such as redis,postgresql,nginx etc. It might be that someone just wants these supporting services without building the local Dockerfiles. Two compose files might be useful depending how prod is deployed..
Popping a docker-compose up/down script in the package.json might be useful
That good idea. Could you help me add this to script and embed env ?
Usually I've only used docker-compose locally in dev to setup the supporting services such as redis,postgresql,nginx etc. It might be that someone just wants these supporting services without building the local Dockerfiles. Two compose files might be useful depending how prod is deployed..
Popping a docker-compose up/down script in the package.json might be useful
What do you mean by "popping a docker-compose up/down script in the package.json"?
Also in this context, I'd assume we could use something like docker swarm to unify these multiple docker compose environments. cc: @joshua-mo-143
@blackmouse572 @believemanasseh This is now a duplicate/stale/old PR?
@blackmouse572 @believemanasseh This is now a duplicate/stale/old PR?
Yeah
Docker compose will run
3000
port5000
port27017
port6397
portYou can also config the env at
compose.yml
otherwise, the default values:REDIS_PASSWORD=eYVX7EwVmmxKPCDmwMtyKVge8oLd2t81
NOTICE : Please run
npm install
to generatepackages.lock
file to make sure the Frontend docker run perfectly.