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
{{ message }}
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.
I've been attempting to run a setup locally involving mongodb, elasticsearch and transporter all on docker.
The dockerization works for all 3, but in order for them to communicate via docker links (which are preferred over exposed ports) the config must have access to environment variables, as docker link addresses/ports are defined in env variables.
This isn't just an issue with docker - anyone using a PaaS that exposes config info via env variables (e.g. heroku) may hit issues here.
Support for environment variables in the config.yaml or via command line args would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
I've been attempting to run a setup locally involving mongodb, elasticsearch and transporter all on docker.
The dockerization works for all 3, but in order for them to communicate via docker links (which are preferred over exposed ports) the config must have access to environment variables, as docker link addresses/ports are defined in env variables.
This isn't just an issue with docker - anyone using a PaaS that exposes config info via env variables (e.g. heroku) may hit issues here.
Support for environment variables in the config.yaml or via command line args would be greatly appreciated!
The text was updated successfully, but these errors were encountered: