Host config value is overridden and not very useful in the first place #65

New Issue

Closed

opened 2019-06-10 09:49:27 +00:00 by b3yond · 1 comment

b3yond commented

2019-06-10 09:49:27 +00:00

Owner

Author: @b3yond Posted at: 06.11.2018 17:55

This happens on the envs branch, with the docker containers.

Expected behavior
The HOST env variable from the .env file is used in the containers.

Actual Behavior
docker exec -ti docker-ticketfrei_backend_1 python3 config.py returns host=0.0.0.0, even if I assigned a real domain.

To Reproduce
Steps to reproduce the behavior:

add HOST=domain to .env
docker-compose up -d
docker exec -ti docker-ticketfrei_backend_1 python3 config.py
See host=0.0.0.0

Screenshots

Additional context
I'm testing the envs branch. #64

Author: @b3yond Posted at: 06.11.2018 17:55 This happens on the envs branch, with the docker containers. **Expected behavior** The HOST env variable from the .env file is used in the containers. **Actual Behavior** `docker exec -ti docker-ticketfrei_backend_1 python3 config.py` returns `host=0.0.0.0`, even if I assigned a real domain. **To Reproduce** Steps to reproduce the behavior: 1. add `HOST=domain` to .env 2. `docker-compose up -d` 3. `docker exec -ti docker-ticketfrei_backend_1 python3 config.py` 4. See `host=0.0.0.0` **Screenshots** ![screenshot_2018-11-06_18-54-31](https://user-images.githubusercontent.com/19255313/48083462-820e1c00-e1f5-11e8-91c7-7d03d2a8721f.png) **Additional context** I'm testing the envs branch. #64

b3yond closed this issue

2019-06-10 09:49:27 +00:00

b3yond commented

2019-06-10 09:49:28 +00:00

Author

Owner

Author: @b3yond Posted at: 07.11.2018 00:51

Apparently the host is only set in the frontend container, but I checked it in the backend container. In the frontend container it's fine.

Author: @b3yond Posted at: 07.11.2018 00:51 Apparently the host is only set in the frontend container, but I checked it in the backend container. In the frontend container it's fine.