Bret Fisher
Bret Fisher
Sure, but also note I'm working on multi-stage myself, but it would be great to compare solutions. I haven't pushed a commit yet so feel free to try using multi-stage...
Since I have multiple multistage examples now listed in the README (which are in other repos), I'm going to move this to a discussion.
I'm happy to review a PR. It sounds like that would just be a change to line 21 to `RUN mkdir -p /opt/node_app/node_modules && chown node:node /opt/node_app`? Also, feel free...
Now that I'm re-reading this a year later, it seems that the problem is the original command is using the wrong location for node_modules, and should be: `docker compose exec...
Using config files is fine, and here are some thoughts: * If you're using Swarm or Kubernetes then they support config files, so where you previously would store `prod.js` on...
1. add that command to the Dockerfile in a RUN line after code is copied in 2. add that to nodemon config so it runs on every node restart for...
Good question, so this would be a good example for this repo so I'll add it as a feature request.
@focux in cases where you need host tools to see node_modules, then you could: 1. Just run npm install on host purely for tools like VSCode. If you’re keeping container...
Did you figure this out? I didn't have time lately to look into this.
Some quick answers without testing: 1. --inspect is on by default in the docker-compose.yml. I guess you're asking about VS Code turning on debugging by default, and I'm not sure....