Closed xNero321 closed 4 years ago
Hi!
If I understood correctly, you are trying to change variable after the first run of the container. That is not going to work, because we are running config generation on the first run only (determined by the absence of /taiga-conf/.initial_setup.lock
file). This is to prevent overwriting user-made changes to configs that are not covered by variables.env (email, auth providers, plugins, etc.).
Hi.
I tried to change the variable before running the command but when my instances are running and go into the taiga-front container the variable TAIGA_HOST
is not changed. Maybe i did something wrong ?
PS: No ssl enable
I can not reproduce this, just changing TAIGA_HOST in variables.env
works as expected. Are you sure there is no lock file present?
$ docker exec taiga-front env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=90c8626fc352
TAIGA_HOST=taiga.mydomain.com
TAIGA_SCHEME=http
TAIGA_BACK_HOST=back
TAIGA_FRONT_HOST=front
EVENTS_HOST=events
TAIGA_SECRET=secret
ENABLE_SSL=no
POSTGRES_HOST=db
POSTGRES_DB=taiga
POSTGRES_USER=postgres
POSTGRES_PASSWORD=password
RABBIT_HOST=rabbit
RABBIT_USER=taiga
RABBIT_PASSWORD=password
RABBIT_VHOST=taiga
REDIS_HOST=redis
REDIS_DB=0
REDIS_PASSWORD=password
NGINX_VERSION=1.17.6
NJS_VERSION=0.3.7
PKG_RELEASE=1
HOME=/root
Hi, i tried to reproduce the same behaviour this morning but everything is working fine. I don't really know what happend the first time...
Hi.
I just cloned your repository to start taiga on my VPS. Once i figured out that
TAIGA_HOST
was not modified in the container. I tried to change it in the filevariables.env
.So i tried to set the variable directly in the compose file. Everything is working fine now, you did a good job. However, is it possible that when i change the variable in the env file, the
TAIGA_HOST
in the container is also changed, rather than adding an env variable in the compose file ?