H2-invent / jitsi-admin

Organize and fully controll your jitsi meet meetings. Make your meeting secure and be sure that only you and your fellows can join your meeting.
https://meetling.de
GNU Affero General Public License v3.0
137 stars 49 forks source link

Instruction about how properly changing environments in docker-compose #525

Open astral0pitek opened 7 months ago

astral0pitek commented 7 months ago

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.

holema commented 7 months ago

Hello, when you edit the .env file, then you need to rerun bash installDocker.sh

astral0pitek commented 7 months ago

I tried, but it change nothing. I was setuping different DEFAULT_LANGUAGE like en, ru and tried to connect ldap to ldap environments in .env but in any way it nothing change. The site still showing German language and not connected to ldap.

astral0pitek commented 6 months ago

So after many many tries in my situation I have: 1) ".env.local" and ".env.prod" files completely not working 2) any environments in .env completely not working 3) keycloak environments not working

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.

holema commented 6 months ago

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. It is corect that the .env variables are not taken from the .env file. there are exportd as environment variables in the installDocker.sh script. This is a not unusual way and is not against any convention.

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 (entwicklung@h2-invent.com). LDAP is not used to login via. YOu always need a Keycloak which you can connect to the LDAP:

holema commented 6 months ago

the default-Langauge paramter will be asked in the install script in the next version.