You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current docker-compose file exposes all internal service ports (including redis and elasticsearch, which both are not even password protected) to the world for no reason at all.
The text was updated successfully, but these errors were encountered:
Thanks for opening an issue about this.
Ports were opened for local development use case, but this is not mentioned in the README or anywhere else for that matter.
WDYT should we create a docker-compose-dev.yml that has ports mappings as they are now and remove port mappings other than 80 and 443 from docker-compose.yml ? (@hevp)
Also README.md should be updated accordingly.
The current docker-compose file exposes all internal service ports (including redis and elasticsearch, which both are not even password protected) to the world for no reason at all.
The text was updated successfully, but these errors were encountered: