normally people start BBB with the pre-built docker images, but for developing you need to build them by yourself. For that you need to ensure that the submodules are also checked out
$ git clone --recurse-submodules https://github.com/bigbluebutton/docker.git bbb-dev
$ cd bbb-devyou can now run bbb-docker locally by simply starting
$ ./scripts/devUse the API Mate with the link presented in the console to create & join a conference.
- the html5 component will watch and automatically reload on any changes 🚀
- if you change anything in the other components, you need to
- manually rebuilt it
$ docker compose build CONTAINERNAME - restart it
$ docker compose up -d CONTAINERNAME
- manually rebuilt it
- if you change any variable in .env, always run following to rebuild the
docker-compose.yml``$ ./scripts/generate-compose` - view the logs with
$ docker compose logs -f - 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)"
- Due to the self signed ssl certificate it is currently not possible to notify greenlight about recordings in dev mode
This always consists out of following steps
- Get an understanding about changes that happened and find out what changes to bbb-docker that require. \
- main source for that are the release notes in https://github.com/bigbluebutton/bigbluebutton/releases
- Apply these changes to this project.
- Often you only need to checkout the git submodules to the specific release tag
- List of all submodules:
git submodule
- List of all submodules:
- Often you only need to checkout the git submodules to the specific release tag
- Test everything (with firefox and chromium/chrome)
- Audio
- Video
- Presentation upload
- Shared Notes
- Create a
CHANGELOG.mdentry - Create a Pull Request
- Receive big thanks from @alangecker