using existing greenlight on the new V3 Bigbluebutton

107 views
Skip to first unread message

Reimar Bauer

unread,
Mar 2, 2025, 5:26:24 AMMar 2
to bigbluebutto...@googlegroups.com
Hi there,
I thought I could just copy the greenlight-v3 dir from my old instance to the new bigbluebutton v3 installation. Verify that it starts and do another bbb-install call. 

The first docker-compose up seems to take longer.

I expect that there may be more steps, because startup now takes a long time

Do you have a description of what I have to do?

Best
Reimar




Jean Pluzo

unread,
Mar 3, 2025, 5:10:51 AMMar 3
to bigbluebutton-greenlight
Hallo Reimar,

as you said, it's not as simple as only copying the GLv3 directory.
I'm currently seeing GLv3 being deployed under /root/greenlight-v3. Of course you should backup this in case something goes wrong. But the main functionallity comes from docker.
GLv3 seems to be using its own container (greenlight-v3) as well as a postgreSQL container (postgres).
Basically you need to backup the database (pg_dump is your friend), copy this db-dump to your new instance, create "empty" (brand new) GLv3 and postgreSQL containers (docker compose) and dump the db inside the new postgreSLQ container.
I've done this a couple of times in GLv2, so I can't say it will work 100% on GLv3. Also, I'm just starting to view the "backbone" of GLv3, so there's that too.
There is a redis container, but I'm not sure (yet) if this is currently being used by GLv3 or Keycloack.
Hope this helps.

VG
J.

Lonesome Walker

unread,
Apr 15, 2025, 4:46:50 PMApr 15
to bigbluebutton-greenlight
It IS quite simple, you just have to take care about that your BBB secret is the same and that's it.
Reply all
Reply to author
Forward
0 new messages