Deployment Overview of BigBlueButton on Server¶

Prerequisites and Basic Requirements¶

To deploy BigBlueButton, the following system requirements must be met:

• Operating System: Ubuntu (specifically the jammy release, as indicated by the installation version jammy-300).

• Privileges: Root access is required to execute the installation script and manage system services.

• Network: The server must have internet access to download the installation script and dependencies.

• Email Configuration: An email address is required during installation for system notifications, defined as info@<domain>.

FQDN of the Final Panel¶

The application is accessible via the following Fully Qualified Domain Name (FQDN) format based on the hostkey.in zone:

• Domain Format: bbb<Server ID>.hostkey.in

• Access URL: https://bbb<Server ID>.hostkey.in

• Protocol: HTTPS is enabled by default.

Replace <Server ID> with the actual numeric identifier of your server instance.

File and Directory Structure¶

The installation script manages the creation of necessary directories and files. Key locations include:

• Installation Script Location: /root/bbb-install.sh

• Data and Configuration: Managed internally by Docker containers; specific paths are abstracted by the containerization layer.

• Certificates: SSL certificates are managed automatically during the installation process for the configured domain.

Application Installation Process¶

The BigBlueButton environment, including the Greenlight management interface, is deployed using the official BigBlueButton installer script.

1. Download the Installer: The installation script is retrieved from the official BigBlueButton GitHub repository.

   curl -o /root/bbb-install.sh https://raw.githubusercontent.com/bigbluebutton/bbb-install/v3.0.x-release/bbb-install.sh
   chmod 755 /root/bbb-install.sh
   

2. Execute the Installation: Run the script with the version jammy-300, specifying the domain and email address. The flags -w (skip firewall checks) and -g (install Greenlight) are included.

   DEBIAN_FRONTEND=noninteractive LANG=C.UTF-8 /root/bbb-install.sh -v jammy-300 -s bbb<Server ID>.hostkey.in -e info@bbb<Server ID>.hostkey.in -w -g
   

3. Post-Installation Verification: The installer automatically verifies that the Greenlight service is responding and initializes the administrative user.

Docker Containers and Their Deployment¶

BigBlueButton and Greenlight are deployed as Docker containers. The installer script handles the orchestration of these containers.

• Greenlight Container: Identified as greenlight-v3. This container hosts the web interface for managing meetings.

• BigBlueButton Core: Runs within separate Docker containers managed by the installation script to handle video conferencing services.

• Initialization: The greenlight-v3 container is started, and a default administrator account is created within it if one does not already exist.

Databases¶

Database configurations are handled automatically by the installation script.

• Storage: Database volumes are mounted to the host system or managed within the Docker layer by the bbb-install.sh script.

• Connection: Applications connect to the database via internal Docker networking. Manual configuration of database connection strings is not required for the standard deployment.

Proxy Servers¶

The deployment utilizes a built-in reverse proxy configuration to handle traffic for the BigBlueButton domain.

• SSL/TLS: HTTPS is enforced. SSL certificates are generated and configured for the domain bbb<Server ID>.hostkey.in.

• Domain Routing: The proxy routes traffic to the respective BigBlueButton and Greenlight services based on the configured FQDN.

• Certbot: The installer manages certificate generation and renewal automatically.

Available Ports for Connection¶

The following ports are utilized by the BigBlueButton environment:

• Port 443: HTTPS traffic for the web interface (Greenlight) and BigBlueButton.

• Port 80: HTTP traffic (typically used for SSL certificate verification or redirects).

The installation script configures the firewall to allow traffic on these necessary ports.

Starting, Stopping, and Updating¶

Service management is performed using Docker commands. The BigBlueButton service management is abstracted, but individual containers can be controlled.

• Check Container Status:

  docker ps -a
  

• Access the Greenlight Container for Management:

  docker exec -it greenlight-v3 /bin/bash
  

• Restart Services: To restart the Greenlight service specifically:

  docker restart greenlight-v3
  

  To restart the entire BigBlueButton stack, standard Docker commands or the bbb-conf tool (installed by the script) can be used to manage the container lifecycle.

Access Rights and Security¶

• Firewall: The installer configures the firewall to restrict access to only necessary ports (80 and 443).

• User Account: An initial administrator account is created within the Greenlight application with the following credentials:

  • Email: [email protected]

  • Role: Administrator

  • Status: Verified

• Restrictions: The system enforces SSL/TLS connections; unencrypted HTTP requests are redirected to HTTPS.

Location of Configuration Files and Data¶

Configuration data is primarily stored within the Docker containers and volumes managed by the bbb-install.sh script.

• Main Script: /root/bbb-install.sh

• Application Data: Stored in Docker volumes associated with the greenlight-v3 and other BigBlueButton containers.

• Logs: Logs can be viewed via Docker command line tools (e.g., docker logs greenlight-v3).