mirror of
https://github.com/bigbluebutton/docker.git
synced 2024-11-29 03:23:18 +01:00
1.6 KiB
1.6 KiB
bbb-docker Development
Running
you can run bbb-docker locally without any certificate issues with following .env
configurations:
DEV_MODE=true
ENABLE_HTTPS_PROXY=true
#ENABLE_COTURN=true
#ENABLE_GREENLIGHT=true
#ENABLE_WEBHOOKS=true
#ENABLE_PROMETHEUS_EXPORTER=true
#ENABLE_RECORDING=true
DOMAIN=10.7.7.1
EXTERNAL_IPv4=10.7.7.1
STUN_IP=216.93.246.18
STUN_PORT=3478
TURN_SERVER=turns:localhost:465?transport=tcp
TURN_SECRET=SuperTurnSecret
SHARED_SECRET=SuperSecret
ETHERPAD_API_KEY=SuperEtherpadKey
RAILS_SECRET=SuperRailsSecret
# ====================================
# CUSTOMIZATION
# ====================================
[... add rest of sample.env here ...]
- regenerate
docker-compose.yml
$ ./scripts/generate-compose
- you can than start it with
$ docker-compose up -d
- view the logs with
$ docker-compose logs -f
- and access the API via
https://mconf.github.io/api-mate/#server=https://10.7.7.1/bigbluebutton/api&sharedSecret=SuperSecret- At some point your browser will warn you about an invalid certificate, but you can press "Accept the Risk and Continue" / "Proceed to 10.7.7.1 (unsafe)"
Notes
- Joining a room via Greenlight currently leads to a "401 session not found" error (see https://github.com/alangecker/bigbluebutton-docker/issues/66). Use the API Mate instead
Changes
- After doing some changes you usually must...
- recreate
docker-compose.yml
$ ./scripts/generate-compose
- rebuild the image(s):
$ docker-compose build [containername]
- restart changes image(s):
$ docker-compose up -d
- recreate