Expose development docker ports on all interfaces by default?
I have noticed that the docker compose setup for development (and also CI and testing) exposes all ports on all interfaces by default, instead of limiting them to localhost. I can think of two advantages, and one (obvious) disadvantage of this:
-
Maybe it's useful for testing mobile apps against a development environment (by pointing the mobile app at the development machine)
-
Quickly being able to show WIP progress to other people on the same network (in this case, exposing "user facing" ports makes sense, but something like the database still doesn't need to be exposed to the network)
-
Obviously, exposing your dev environment to whatever network you're in might pose arbitrary security implications, or potential for random people to mess with you ;) (While this is mitigated by using a properly restricted firewall, many "desktop" operating systems don't ship this as a default)
I would have made a merge request already, but I first wanted to hear opinions and possible angles I have not yet considered :)