The configuration folders below your
CONFIG=~/.jitsi-meet-cfg directory are mounted into the respective containers. So you should
Remove the containers:
Delete the outdated configuration
rm -rf ~/.jitsi-meet-cfg/* # adjust to your CONFIG dir
Now adjust the settings in your
.env file. You will probably want the
internal authentication with guests enabled, so
# Enable authentication
# Enable guest access
# Select authentication type: internal, jwt or ldap
Now start the containers. Once they are up you need to create the users within prosody container:
docker-compose up -d
docker-compose exec prosody /bin/bash
# the following is entered in the prosody container for each user that is allowed to create conferences
# you may need to adjust <meet.jitsi> if you changed it in the .env file
prosodyctl --config /config/prosody.cfg.lua register <username> <meet.jitsi> <password>
Note: the above was mostly written from the top of my head and may contain typos and possibly mistakes, so I’d recommend you to read the comments in the
.env file, check the Jitsi Handbook and search the forum for existing posts if in doubt.
I don’t think thats possible with docker-jitsi-meet currently.
There are workarounds for remembering a room’s password, see here. However, if authentication is configured, only an authenticated user can “re-open” a room.