-
Notifications
You must be signed in to change notification settings - Fork 31
Greenlight 2/3 Import: Preparations for import of recordings #3034
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Changes from all commits
f31613a
cbdb59a
09888e5
fe44731
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -3,7 +3,7 @@ title: Migrate from Greenlight | |||||
| description: Step by step guide to migrate from Greenlight to PILOS | ||||||
| --- | ||||||
|
|
||||||
| PILOS provides an easy to use command to import all Greenlight users (incl. ldap), rooms and shared accesses. | ||||||
| PILOS provides an easy to use command to import all Greenlight users (incl. ldap), rooms (incl. default presentation) and shared accesses. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix compound adjective hyphenation. The phrase "easy to use" should be hyphenated when used as a compound adjective before a noun. 📝 Proposed grammar fix-PILOS provides an easy to use command to import all Greenlight users (incl. ldap), rooms (incl. default presentation) and shared accesses.
+PILOS provides an easy-to-use command to import all Greenlight users (incl. ldap), rooms (incl. default presentation) and shared accesses.📝 Committable suggestion
Suggested change
🧰 Tools🪛 LanguageTool[grammar] ~6-~6: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) 🤖 Prompt for AI Agents |
||||||
|
|
||||||
| ## Preparing migration from other host | ||||||
|
|
||||||
|
|
@@ -31,9 +31,9 @@ Successfully imported presentation files will be copied to a different location. | |||||
|
|
||||||
| ## Running migration command | ||||||
|
|
||||||
| The command will output the process of the import and informs about failed user, room and shared access import. | ||||||
| The command will output the process of the import and informs about failed user, room, room presentation and shared access import. | ||||||
|
|
||||||
| **Note** If a room with the same room id already exists in PILOS it will NOT be imported and the shared accesses are ignored. | ||||||
| **Note** If a room with the same room id already exists in PILOS it will NOT be imported and its default presentation and shared accesses are ignored. | ||||||
|
|
||||||
| ### Greenlight 2 | ||||||
|
|
||||||
|
|
@@ -135,6 +135,25 @@ docker compose exec app pilos-cli import:greenlight-v3 \ | |||||
| 12345678 | ||||||
| ``` | ||||||
|
|
||||||
| ## Importing recordings | ||||||
|
|
||||||
| You can also import recordings for existing rooms. To make this possible the import command creates a meeting with the BBB meeting ID for every imported room. | ||||||
| This meeting does not have a start- or end timestamp, so it not visible in the frontend. Associated recordings _will_ be listed, however. | ||||||
|
|
||||||
| To import existing recordings, you have to | ||||||
|
|
||||||
| 1. find the meeting ID (column `bbb_id` (GL2) or `meeting_id` (GL3) in the `rooms` table) | ||||||
| 2. find all recordings with this meeting ID (XPath: `/recording/meta/meetingId` in metadata.xml) | ||||||
| 3. pack matching recordings into tar files and | ||||||
| 4. move or copy those tar files to PILOS' `recordings-spool` directory. | ||||||
|
coderabbitai[bot] marked this conversation as resolved.
|
||||||
|
|
||||||
| Existing recordings prepared like this will be imported just like new ones would. | ||||||
|
|
||||||
| **Note** You _may_ have to temporarily increase RAM allocated to horizon if it is limited. | ||||||
|
|
||||||
| **Note** YMMV, depending on your BBB loadbalancer. If, for example, you run b3scale, you need to extract the "simple" Greenlight meeting ID from the | ||||||
| more complex b3scale meeting ID. | ||||||
|
|
||||||
| ## Adjust nginx | ||||||
|
|
||||||
| ### PILOS is running on the same host | ||||||
|
|
||||||
Uh oh!
There was an error while loading. Please reload this page.