This page describes some common processes for our BigBlueButton instance. The user-facing documentation is here.
Upgrades should be done carefully. Read the changelog carefully to check for breaking changes.
Before running an upgrade, check whether there are planned or ongoing meetings. You can use /root/bin/bbb-stats.py to identify current meetings.
# Save old BBB configuration bbb-conf --check > YYYYMMDD-pre-update-conf.txt # Update and upgrade apt update apt upgrade # Set IP for server bbb-conf --setip conf.fsfe.org # Save new and compare BBB config bbb-conf --check > YYYYMMDD-post-update-conf.txt diff YYYYMMDD-pre-update-conf.txt YYYYMMDD-post-update-conf.txt
It might make sense to reboot the server afterwards.
Greenlight is the user interface for the BBB server. We've made some customisations, therefore the upgrade may be a bit more complex. The goal is to have our customisations on branch custom-fsfe, and merge in the latest upstream (in this example tag release-2.X.X).
cd ~/greenlight git checkout custom-fsfe git fetch origin git merge release-2.X.X # it might be necessary to resolve some conflicts here # Build new local image scripts/image_build.sh greenlight-custom release-2.X.X # Edit the custom docker-compose file, and change the version number of the custom greenlight image to 2.X.X # Restart the container docker-compose -f docker-compose-custom.yml down docker-compose -f docker-compose-custom.yml up -d
Renaming a room is only possible via root access to the server. So, run as root:
docker exec -it greenlight-v2 bash # inside of the container bundle exec rails c # inside of this shell Room.find_by(uid: "CURRENT_ROOM_ID").update_attribute(:uid, "NEW_CUSTOM_ID")
CURRENT_ROOM_ID is something like "use-123-abc-456".