VinceHillier
commented
4 years ago variables.env updates never make it to the container because there are dangling locks.
These components make use of the file lock: back, front, and proxy.
https://github.com/docker-taiga/back/blob/master/start.sh#L5-L7 https://github.com/docker-taiga/front/blob/master/start.sh#L3-L5 https://github.com/docker-taiga/proxy/blob/latest/start.sh#L3-L6
I cannot see a good reason for this lock on these components as they are just configuration updates. Their presence prevents modification of variables in the future and a broken frontend as seen above.
I can submit a PR to remove the locking I just want to make sure I'm not missing something (feel free to chime in here @w1ck3dg0ph3r ) :)
TLDR: lock files prevent variables.env from being updated. If you ever started taiga, modified the TAIGA_HOST, then restarted your changes won't be reflected in the configuration files.
Quick fix:
1) Edit variables.env until satisfied
2) Remove lock files. Run in directory you have docker-taiga checked out in.
find . -name .initial_setup.lock -exec rm -v {} \;
3) docker-compose restart
w1ck3dg0ph3r
As suggested in #18
variables.env
logs from docker-compose up
This is result: