-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instruction about how properly changing environments in docker-compose #525
Comments
Hello, |
I tried, but it change nothing. |
So after many many tries in my situation I have:
The docker-compose project just only running. When I see a docker-compose project I expect the project to follow the concept where I will only need to change the parameters in the ".env" file and run the project using "docker-compose -up -d". In this project, the project setting only works where the "docker.conf" file is created by script and nowhere else. |
Hello @astral0pitek, the DEFAULT LANGUAGE unfortunentalls is not support by the libry so the env is not used by the system. We try to fix this in the future. For The LDAP: This part is nowhere documented and this is not by excuse not documented it is on purpose not documented. This feature would make you a lot of troubble and is only to preload the users into the adressbook. This feature would cause us tons of issues so it is only used when we support the jitsi-admin on our customers. You can have an instruction but forthi please contact our development team ([email protected]). LDAP is not used to login via. YOu always need a Keycloak which you can connect to the LDAP: |
the default-Langauge paramter will be asked in the install script in the next version. |
Please may you create instruction about how to change environments properly?
I runned "bash ./installDockerDebian.sh", everything ok. But what next? I changing environments in .env file but it doing literally nothing!
Also please add instruction about how to run containers after installation after you change .env file.
The text was updated successfully, but these errors were encountered: