Using Docker in your development workflow has a positive impact on your productivity. It eliminates the typical "It worked on my machine" type of b...
For further actions, you may consider blocking this person and/or reporting abuse
Jakob Klamser on October 06, 2020
For further actions, you may consider blocking this person and/or reporting abuse
I love Docker for prod deployments but when using it in dev environments it‘d have to rebuild and re-run the image every time I change something in the code in order to see the result, correct? Any solution to this?
Actually no, in this example your volume is connected to the container. So every time you change something, for example, in server.js it automatically updates your "localhost".
I recommend trying out this setup ;)
Oh, I didn’t notice that! That‘s a great way to solve this problem. Thanks, great post! :-)
I tried Nodedock (github.com/nodedock/nodedock) Which has some pre configured services, and can be configured further with .env file.
Keep in mind if you use some node tools which normally would run on 127.0.0.1 might need to bind 0.0.0.0 in their respective configs.
Nice one! I need to try it :)
You have managed to not overcomplicate things and yet explain the topic very well. Great job and thank's!
Thanks for the awesome feedback
Good introduction into Docker.
If you put the same article as a readme.md in your repos it will be great Jakob.
Maybe I will do that. Need to think about it