Installing BigBlueButton on Ubuntu 16.04

Good day, today I decided to write my first post at the end.

I will not tell much about BigBlueButton, further BBB, I will only say that BBB is:

• Free (GNU Lesser General Public License).
• For Video-Audio Conferences.
• For presentations.
• For webinars.

Let's get started

A little background.

In our case, we use Ubuntu 16.04 x64 and I advise you on the same)

For full BBB operation, you need:

1. Static external IP.
2. Bound domain name.
3. SSL Certificate.
4. Forwarded Ports.

Part one

Quick installation script

The estimated installation time is 15-20 minutes.
Installation is simple and not intrusive.

In this case, the installation is using external IP.

wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-200 

With the use of the external domain name bbb.example.com

 wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-200 -s bbb.example.com 

Using the external domain name bbb.example.com and obtaining an SSL certificate from
Let's Encrypt using Email info@example.com

 wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-200 -s bbb.example.com -e info@example.com 

SSL + latest HTML5 Client

  wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-200 -s bbb.example.com -e info@example.com -t 

SSL + GreenLight

 wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-200 -s bbb.example.com -e info@example.com -g 

All of the above

 wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-200 -s bbb.example.com -e info@example.com -t -g 

It remains to wait for the installation to complete.

Then I thought about not tormenting the reader and not writing the second part together with the first one, but I remembered that there is still a part with manual installation.

Part two

Quick docker installation

On the BBB website there is a list of what we won’t get to the docker version.

• Nginx does not have an SSL certificate, so you need to use FireFox to use WebRTC audio / video.
• Processes run using supervisord (instead of systemd)
• HTML5 client supports video, but not desktop sharing using WebRTC

That is, you will not send it to production.

But nevertheless I will describe, suddenly to whom for tests it will be interesting.

By the way, if you hide it behind reverse proxy with SSL, then everything should start up on the idea (I didn’t check it myself).

 docker run -p 80:80/tcp -p 443:443/tcp -p 1935:1935 -p 5066:5066 -p 3478:3478 -p 3478:3478/udp bigbluebutton/bigbluebutton -h LOCAL_IP_ADDRESS 

Well, as if everything. My next article will be about manual installation of all this fun, unless of course it is missed.

Fin.