How to revert back to greenlight-v2?

[dashohoxha]

Maybe greenlight-v3 is better than greenlight-v2 for an initial installation (for reasons that I don't understand). However, as long as there is no clean and easy migration path from v2 to v3, I'd like to stick to greenlight-v2.

I still have the old directory greenlight/, which I assume preserves all the necessary data. So, I believe that it should be possible to switch back to greenlight-v2. Any advice on how to do it? I don't think that it should be too difficult.

[ffdixon]

which I assume preserves all the necessary data. So, I believe that it should be possible to switch back to greenlight-v2

Right. You should be able to start/stop either greenlight with their associated docker-compose command.

[dashohoxha]

You should be able to start/stop either greenlight with their associated docker-compose command.

I tried these:

cd /root/greenlight-v3/
docker-compose down
cd /root/greenlight/
docker-compose up -d

Then I had to fix the nginx configuration:

1. On /etc/nginx/sites-available/bigbluebutton I replaced:

     # BigBlueButton landing page.
     location / {
       root   /var/www/bigbluebutton-default/assets;
       try_files $uri @bbb-fe;
     }
   

   with:

     # BigBlueButton landing page.
     location = / {
       return 301 https://$server_name/b;
     }
     location /b {
       root   /var/www/bigbluebutton-default/assets;
       try_files $uri @bbb-fe;
     }
   

2. On the directory /usr/share/bigbluebutton/nginx I renamed greenlight-v3.nginx to greenlight-v3.nginx.disabled. Then modified greenlight.nginx by replacing location /b { with location @bbb-fe {.

3. Reload nginx: systemctl reload nginx.

For some reasons, I had also to update BIGBLUEBUTTON_SECRET on /root/greenlight/.env, and the rebuild it:

cd /root/greenlight/
bbb-conf --secret
vim .env
docker-compose down
docker-compose up -d

It seems to work. I hope that I have not missed any other steps that are required.

Anyway, I guess that next time that I try to update (by running bbb-install-2.6.sh) I may have to repeat some of these steps again.

[dashohoxha]

Then I had to fix the nginx configuration:

You know what? It is possible to run both gl-v2 and gl-v3 at the same time. The only nginx modification that is needed is this:

Edit the file /usr/share/bigbluebutton/nginx/greenlight.nginx and replace

location /b {
  proxy_pass          http://127.0.0.1:5000;
[ . . . . . . . . . . . . . . . ]

with this:

location /b {
  root   /var/www/bigbluebutton-default/assets;
  try_files $uri @bbb-gl-v2;
}

location @bbb-gl-v2 {
  proxy_pass          http://127.0.0.1:5000;
[ . . . . . . . . . . . . . . . ]

Of course, both of GL apps need to be started:

cd /root/greenlight/
docker-compose up -d

cd /root/greenlight-v3/
docker-compose up -d

After the migration from v2 to v3 is done properly, I can shutdown gl-v2.

@ffdixon I would suggest that the installation script (bbb-install-2.6.sh) enables both of the GL versions by default.

[dashohoxha]

Edit the file /usr/share/bigbluebutton/nginx/greenlight.nginx and replace

Actually this modification is not needed either. So, no modifications at all on nginx. Just update the BIGBLUEBUTTON_SECRET on /root/greenlight/.env and then start up the gl-v2 app. Then both versions of the greenlight will be available at the same time.

[paulmenzel]

Thank you for documenting all your steps. As running greenlight-v2 seems to work, is there still something to be improved in the install script in this regard?