Skip to content

Commit 8abd75d

Browse files
committed
Minor formatting and doc/readme changes
1 parent 56dc2e6 commit 8abd75d

4 files changed

Lines changed: 12 additions & 5 deletions

File tree

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ Documentation can be found at https://bbblb.readthedocs.io/ or in the `./docs/`
1616
* **Advanced Loadbalancing:** Meetings are distributed based on current and predicted utilization, taking common usage patterns into account.
1717
* **Recording Management:** Recordings are transferred to central storage with a robust post_publish.rb script installed on each BBB backend server. This script just needs to sit in the correct directory, it does not require any configuration, ssh access or shared network file system to work.
1818
* **Callback Relay:** Callbacks registered for a meeting are properly relayed between the back-end BBB server and the front-end application with a robust retry-mechanism.
19+
* **Protected Recordings**: Experimental support for single-use recording links to prevent recording link sharing.
1920
* **Management CLI and API:** BBBLB comes with a rich command line tool to fetch health information, manage tenants, servers or recordings, or automate maintenance tasks.
2021
* **Scalability:** BBBLB is a modern async python application with low overhead and can easily scale to large clusters with thousands of active meetings.
2122

@@ -50,7 +51,8 @@ graph TD
5051

5152
Recordings are stored and managed centrally on the BBBLB server, separated
5253
by tenant, which allows you to remove or replace BigBlueButton servers
53-
without losing access to past recordings.
54+
without losing access to past recordings. Callbacks or webhooks are relayed
55+
though BBBLB back to your front-end application.
5456

5557
Rolling cluster upgrades without downtime are also fully supported. With
5658
`bbblb server disable` you can disable some of your back-end servers

bbblb/migrations/versions/faacfea3b608_protected_recordings.py

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,10 @@ def upgrade() -> None:
3535
),
3636
sa.PrimaryKeyConstraint("uuid", name=op.f("pk_view_tickets")),
3737
)
38-
op.add_column("recordings", sa.Column("protected", sa.Boolean(), server_default=sa.sql.expression.false()))
38+
op.add_column(
39+
"recordings",
40+
sa.Column("protected", sa.Boolean(), server_default=sa.sql.expression.false()),
41+
)
3942
with op.batch_alter_table("recordings") as batch_op:
4043
batch_op.alter_column("protected", server_default=None)
4144

bbblb/services/db.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,9 @@ async def on_start(self):
4848

4949
current, target = await check_migration_state(self._db_url)
5050
if current != target and self._migrate:
51-
LOG.info(f"Migrating database from schema revision {current!r} to {target!r} ...")
51+
LOG.info(
52+
f"Migrating database from schema revision {current!r} to {target!r} ..."
53+
)
5254
await migrate_db(self._db_url)
5355
elif current != target:
5456
LOG.error(f"Expected schema revision {target!r} but found {current!r}.")

docs/index.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,8 +59,8 @@ Features
5959
- **Callback Relay**: Callbacks registered for a meeting are properly
6060
relayed between the back-end BBB server and the front-end application
6161
with a robust retry-mechanism.
62-
- **Protected recordings**: Experimental support for single-use
63-
recording links to prevent [#pr]_ link sharing.
62+
- **Protected Recordings**: Experimental support for single-use
63+
recording links to prevent recording link sharing [#pr]_.
6464
- **Admin API and CLI**: BBBLB offers both an API and a command line
6565
interface to fetch health information, manage tenants, servers or
6666
recordings and perform maintenance tasks.

0 commit comments

Comments
 (0)