bigbluebutton / greenlight

A really simple end-user interface for your BigBlueButton server.
GNU Lesser General Public License v3.0
794 stars 3.8k forks source link

export / import for users / rooms / settings #5419

Open devZer0 opened 1 year ago

devZer0 commented 1 year ago

i think updating bbb 2.5 to 2.6 or 2.7. is totally complicated and things would be much simpler, if we had some way to backup greenlight data like users, rooms and settings to a logical backup / export and be able to import that in a later version of greenlight.

could you please make greenlight upgrade more straightforward or provide export / import function?

i consider stop using bbb with greenlight because of upgrade hassle v2->v3 at the moment. it simply sucks

farhatahmad commented 12 months ago

The migration of v2 -> v3 is essentially just

  1. Run them side by side
  2. Connect them with 2 env variables
  3. Run 4 commands

Not sure why this is considered too complicated? What steps are you having trouble with?

lkrbbsb commented 11 months ago

We currently have the same issue: even that we were able to migrate, there were several issues. Seems that v3 is not really production-ready.

farhatahmad commented 11 months ago

We've migrated multiple deployments with thousands of users each. If you're having an issue, please make a detailed post with the issues you're running into so that we can help guide you

PhilippKilian commented 10 months ago

@farhatahmad we also have the same issue:

we want to migration from v2->v3 with the following setup:

Migration of roles, rooms and setting are working, but the migration of user only partial.

So it's currently an issue for us to migrate from v2 to v3 only by the given migrations tasks from the documentation.

PhilippKilian commented 10 months ago

@farhatahmad we also have the same issue:

we want to migration from v2->v3 with the following setup:

* Greenlight-v2 version: `v2.14.8.4`

* Greenlight-v3 version: `v3.0.9.1`

* `SECRET_KEY_BASE` of v2 and v3 and `V3_SECRET_KEY_BASE` are identical

* both running on different machines under different DNS names

Migration of roles, rooms and setting are working, but the migration of user only partial.

* user migrations have all necessary data

* the `password_digest` between v2 and v3 are different for Greenlight provided users (local users), the user login in the v3 Greenlight system fails

* if the `password_digest` in the v3 database is updated manually with the value of the v2 database, the login in the v3 Greenlight is successful

So it's currently an issue for us to migrate from v2 to v3 only by the given migrations tasks from the documentation.

it works fine if version v3.1 or higher is used for greenlight-v3 side