| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| computing:nmbbb [2021/04/03 03:32] – oemb1905 | computing:nmbbb [2022/11/12 05:23] (current) – oemb1905 |
|---|
| ------------------------------------------- | ------------------------------------------- |
| |
| This tutorial is for folks who have a need for a [[https://docs.bigbluebutton.org/|Big Blue Button]] instance. In my case, I am a teacher and I need a reliable digital instructional platform that is also full of features ... and floss. BBB is the only choice for these requirements. Moreover, it also helps with a specific //thinking routine// I developed, called [[https://youtu.be/lOKaVAsyDaY|Inquirer Presenter Scribe]]. The platform and the approach together provide a rich opportunity for mathematical seminar and other forms of pedagogy. This service will, furthermore, be available to all New Mexico educators for free - schedule details will be released when/if the project reaches full maturity, which we hope it will. This will be the official wiki for documentation of configs, setup, etc. The status page is [[https://haacksnetworking.com/2021/03/31/nm-community-big-blue-button-project/|over at my business website]]. Alright, more later folks. | This tutorial is for setting up a BBB instance using their installer script. In my case, this instance will run in a virtualized environment on a physical host with a symmetric gig connection. |
| |
| ------------------------------------------- | ------------------------------------------- |
| Step #1 | Step #1 |
| |
| I have found from trial and error that for some reason it helps to set up a basic apache web server first, disable it, then run their script. If you don't know how to do this, see the [[https://wiki.haacksnetworking.com/doku.php?id=computing:apachesurvival|apachesurvival]] tutorial but do not add php and mysql/mariadb. Just prior to running the bbb-install.sh script they provide, remove the apache2 package. Once the script completes, simply reinstall the certbot packages and then debug from there. There are long reasons for this - but, in short, it is because of how Ubuntu 16 - required for BBB - works with certbot and TLS. From here, once the basic instance is up, we switch to setting up greenlight, which we do as follows. Again, I am using the guide I cited above, so follow along as I use that to set up this particular instance. | Okay, so I installed a clean Ubuntu 18.04.6 on a VM with 8 processors and 16GB RAM. I used the install script found at the [[https://docs.bigbluebutton.org/2.3/install.html#Install_|BBB documentation/install website]]: |
| | |
| | wget -qO- https://ubuntu.bigbluebutton.org/bbb-install-2.5.sh | bash -s -- -v focal-250 -s bbb.example.com -e notice@example.com -a -w |
| | |
| | Since my data center does not support ipv6, I needed to disable this. I am working with Brown Rice to make ipv6 a reality, but all in good time. BBB ipv6 [[https://docs.bigbluebutton.org/support/troubleshooting.html#freeswitch-fails-to-bind-to-port-8021|disable resource]]. |
| | |
| | sudo nano /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml |
| | <param name="listen-ip" value="127.0.0.1"/> |
| | sudo mv /opt/freeswitch/etc/freeswitch/sip_profiles/internal-ipv6.xml /opt/freeswitch/etc/freeswitch/sip_profiles/internal-ipv6.xml_ |
| | sudo mv /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml_ |
| | |
| | It is now time to set up Greenlight. |
| |
| mkdir ~/greenlight | mkdir ~/greenlight |
| cd ~/greenlight | cd ~/greenlight |
| | |
| | If you lock yourself out of admin account after a vanilla install. |
| | |
| | docker run --rm bigbluebutton/greenlight:v2 cat ./sample.env > .env |
| | docker run --rm bigbluebutton/greenlight:v2 bundle exec rake secret |
| | sudo bbb-conf --secret |
| | docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check |
| | docker run --rm bigbluebutton/greenlight:v2 cat ./greenlight.nginx | sudo tee /etc/bigbluebutton/nginx/greenlight.nginx |
| | sudo systemctl restart nginx |
| | |
| | Now, let's start greenlight: |
| | |
| | cd ~/greenlight |
| | docker-compose -v |
| | mkdir /etc/bigbluebutton/nginx/ |
| | touch /etc/bigbluebutton/nginx/greenlight.nginx |
| | docker run --rm bigbluebutton/greenlight:v2 cat ./docker-compose.yml > docker-compose.yml |
| | export pass=$(openssl rand -hex 24); sed -i 's/POSTGRES_PASSWORD=password/POSTGRES_PASSWORD='$pass'/g' docker-compose.yml;sed -i 's/DB_PASSWORD=password/DB_PASSWORD='$pass'/g' .env |
| | docker-compose up -d |
| | |
| |
| --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/04/02 21:25// | --- //[[jonathan@haacksnetworking.org|oemb1905]] 2022/11/11 22:12// |
