|
|
|
@@ -16,54 +16,43 @@ the following command inside your docker container:
|
|
|
|
|
|
|
|
|
|
## [Unreleased]
|
|
|
|
|
|
|
|
|
|
### Marketing / Brevo integration now uses `django-lasuite`
|
|
|
|
|
### Purging inactive rooms
|
|
|
|
|
|
|
|
|
|
The in-house marketing service (`core.services.marketing`) has been removed and
|
|
|
|
|
replaced by the shared implementation from `django-lasuite`
|
|
|
|
|
(`lasuite.marketing`). This fixes a bug where updating a user's contact on
|
|
|
|
|
Brevo overwrote their list memberships, removing lists set by other
|
|
|
|
|
La Suite products. Existing lists are now preserved and merged.
|
|
|
|
|
Rooms now keep track of the last time they were started (`last_started_at`), fed by LiveKit's `room_started` webhook. A new `purge_inactive_rooms` management command permanently deletes the rooms that have not been started for `ROOM_INACTIVITY_DELETION_DAYS` days. See [the room purge documentation](docs/features/room-purge.md).
|
|
|
|
|
|
|
|
|
|
**Celery worker required.** Newsletter signup on login
|
|
|
|
|
(`SIGNUP_NEW_USER_TO_MARKETING_EMAIL=True`) is now dispatched as an
|
|
|
|
|
asynchronous Celery task (`lasuite.marketing.tasks.create_or_update_contact`)
|
|
|
|
|
instead of a synchronous call with a 1s timeout. Make sure a Celery worker is
|
|
|
|
|
running alongside the backend, otherwise contacts will never be pushed to Brevo.
|
|
|
|
|
- The feature is **disabled by default**: nothing is deleted unless you set `ROOM_INACTIVITY_DELETION_DAYS`.
|
|
|
|
|
- The migration marks every existing room as started at the time of the upgrade, so no existing room can be purged before a full inactivity period has elapsed after upgrading.
|
|
|
|
|
- Rooms holding a saved recording their users may still access are kept: any saved recording, or, when `RECORDING_EXPIRATION_DAYS` is set, a saved recording created within that window.
|
|
|
|
|
- Inactivity is measured from LiveKit's `room_started` webhook: if it is not delivered to your backend, rooms in daily use look inactive and get purged.
|
|
|
|
|
- When a room is purged, all it's configuration and access rights are also deleted. Its slug becomes available again and can be reused when a meeting is created from that same URL.
|
|
|
|
|
|
|
|
|
|
**Configuration changes.** The following environment variables / settings are
|
|
|
|
|
**removed** and no longer read:
|
|
|
|
|
* With `ALLOW_UNREGISTERED_ROOMS=false`, only an authenticated user can navigate to a previously existing link after the room has been purged. Doing so recreates the room in the database with a fresh configuration, with that user associated with it and granted admin rights.
|
|
|
|
|
* With `ALLOW_UNREGISTERED_ROOMS=true`, any user can reopen the purged room by navigating to the same URL. In that case, the room is created dynamically and no corresponding room entry is persisted in the database.
|
|
|
|
|
|
|
|
|
|
- `MARKETING_SERVICE_CLASS`
|
|
|
|
|
- `BREVO_API_KEY`
|
|
|
|
|
- `BREVO_API_CONTACT_LIST_IDS`
|
|
|
|
|
- `BREVO_API_CONTACT_ATTRIBUTES` (previous default: `{"VISIO_USER": True}`)
|
|
|
|
|
- `BREVO_API_TIMEOUT`
|
|
|
|
|
### Local development: MinIO replaced by Garage
|
|
|
|
|
|
|
|
|
|
They are replaced by a single `LASUITE_MARKETING` setting, configured through:
|
|
|
|
|
The development stacks now use [Garage](https://garagehq.deuxfleurs.fr/) instead of MinIO as S3 storage. Garage keeps its own format in `data/media/meta` and `data/media/data` and cannot read what MinIO left there, so local recordings and files will be lost.
|
|
|
|
|
|
|
|
|
|
| Variable | Default | Description |
|
|
|
|
|
| ------------------------------ | ------------------------------------------------ | -------------------------------------------- |
|
|
|
|
|
| `LASUITE_MARKETING_BACKEND` | `lasuite.marketing.backends.dummy.DummyBackend` | Backend class path |
|
|
|
|
|
| `LASUITE_MARKETING_PARAMETERS` | `{}` | Keyword arguments passed to the backend |
|
|
|
|
|
To migrate a local environment:
|
|
|
|
|
|
|
|
|
|
⚠️ The default backend is now a **dummy** (no-op). If you previously used
|
|
|
|
|
Brevo, you must explicitly configure it, otherwise signups are silently dropped:
|
|
|
|
|
1. Stop the stack and remove its containers, including the former `minio` one: `docker compose down --remove-orphans`
|
|
|
|
|
2. Optionally reclaim the space used by MinIO: `rm -rf data/media && make data/media`
|
|
|
|
|
3. In your `env.d/development/*` files, replace `minio:9000` by `garage:9000`, the `meet` / `password` credentials by `meet-access-key` / `meet-secret-access-key`, and add `AWS_S3_REGION_NAME=local` (or delete these files and run `make create-env-files`)
|
|
|
|
|
4. Run `make create-env-files` to generate `env.d/development/garage`, which holds a random RPC secret for Garage.
|
|
|
|
|
5. Rebuild the images, since the summary and agent images now install boto3 instead of minio
|
|
|
|
|
|
|
|
|
|
LASUITE_MARKETING_BACKEND=lasuite.marketing.backends.brevo.BrevoBackend
|
|
|
|
|
LASUITE_MARKETING_PARAMETERS={"api_key": "<your-brevo-api-key>", "api_contact_list_ids": [1, 2], "api_contact_attributes": {"VISIO_USER": True}}
|
|
|
|
|
### Summary service and metadata collector: boto3 replaces the minio client
|
|
|
|
|
|
|
|
|
|
Migration mapping:
|
|
|
|
|
The summary service and the metadata collector agent now talk to S3 through boto3 instead of the minio client, with the same settings.
|
|
|
|
|
Requests are now signed for `AWS_S3_REGION_NAME` as-is. When it is not set, the region is no longer looked up from the bucket: boto3 falls back to `AWS_DEFAULT_REGION`, then to `us-east-1`. If you left `AWS_S3_REGION_NAME` unset, set it to your provider's region before upgrading, or providers that check the signing region will reject the transcripts, summaries and meeting metadata uploads, as well as their signed URLs.
|
|
|
|
|
|
|
|
|
|
- `BREVO_API_KEY` → `api_key`
|
|
|
|
|
- `BREVO_API_CONTACT_LIST_IDS` → `api_contact_list_ids`
|
|
|
|
|
- `BREVO_API_CONTACT_ATTRIBUTES` → `api_contact_attributes` (re-add
|
|
|
|
|
`{"VISIO_USER": True}` if you relied on the old default)
|
|
|
|
|
- `BREVO_API_TIMEOUT` → no equivalent (the request runs in a background task)
|
|
|
|
|
Also:
|
|
|
|
|
- Signed URLs to transcripts and summaries are now always path-style (`<endpoint>/<bucket>/<key>`), whereas the minio client used virtual-hosted-style URLs
|
|
|
|
|
- The metadata collector now accepts `AWS_S3_ENDPOINT_URL` with or without a scheme, like the summary service: the scheme always follows `AWS_S3_SECURE_ACCESS`.
|
|
|
|
|
|
|
|
|
|
Note: `BREVO_API_KEY` used to support being read from a secret file; the API key
|
|
|
|
|
now lives inside `LASUITE_MARKETING_PARAMETERS`, so adapt how you inject that
|
|
|
|
|
secret (e.g. build the whole variable from your secret store).
|
|
|
|
|
### Helm chart: media services default to Garage
|
|
|
|
|
|
|
|
|
|
The `meet` chart now defaults `serviceMedia.host` and `serviceMediaFiles.host` to `garage.meet.svc.cluster.local`, and the `upstream-vhost` annotation of `ingressMedia` and `ingressMediaFiles` to `garage.meet.svc.cluster.local:9000`. If you relied on the former `minio.meet.svc.cluster.local` defaults, set these values explicitly to your S3 service before upgrading, or recordings and files stop being served under `/media`.
|
|
|
|
|
### Recording encoding settings replaced by a resolution/profile model
|
|
|
|
|
|
|
|
|
|
The `RECORDING_ENCODING_*` settings introduced in v1.16.0 exposed raw encoder
|
|
|
|
@@ -186,46 +175,6 @@ Before enabling it:
|
|
|
|
|
See [docs/features/recording.md](docs/features/recording.md#tuning-recording-encoding)
|
|
|
|
|
for the full setting reference, the shipped profile table and the tuning caveats.
|
|
|
|
|
|
|
|
|
|
## v1.33.0
|
|
|
|
|
|
|
|
|
|
### Purging inactive rooms
|
|
|
|
|
|
|
|
|
|
Rooms now keep track of the last time they were started (`last_started_at`), fed by LiveKit's `room_started` webhook. A new `purge_inactive_rooms` management command permanently deletes the rooms that have not been started for `ROOM_INACTIVITY_DELETION_DAYS` days. See [the room purge documentation](docs/features/room-purge.md).
|
|
|
|
|
|
|
|
|
|
- The feature is **disabled by default**: nothing is deleted unless you set `ROOM_INACTIVITY_DELETION_DAYS`.
|
|
|
|
|
- The migration marks every existing room as started at the time of the upgrade, so no existing room can be purged before a full inactivity period has elapsed after upgrading.
|
|
|
|
|
- Rooms holding a saved recording their users may still access are kept: any saved recording, or, when `RECORDING_EXPIRATION_DAYS` is set, a saved recording created within that window.
|
|
|
|
|
- Inactivity is measured from LiveKit's `room_started` webhook: if it is not delivered to your backend, rooms in daily use look inactive and get purged.
|
|
|
|
|
- When a room is purged, all it's configuration and access rights are also deleted. Its slug becomes available again and can be reused when a meeting is created from that same URL.
|
|
|
|
|
|
|
|
|
|
* With `ALLOW_UNREGISTERED_ROOMS=false`, only an authenticated user can navigate to a previously existing link after the room has been purged. Doing so recreates the room in the database with a fresh configuration, with that user associated with it and granted admin rights.
|
|
|
|
|
* With `ALLOW_UNREGISTERED_ROOMS=true`, any user can reopen the purged room by navigating to the same URL. In that case, the room is created dynamically and no corresponding room entry is persisted in the database.
|
|
|
|
|
|
|
|
|
|
### Local development: MinIO replaced by Garage
|
|
|
|
|
|
|
|
|
|
The development stacks now use [Garage](https://garagehq.deuxfleurs.fr/) instead of MinIO as S3 storage. Garage keeps its own format in `data/media/meta` and `data/media/data` and cannot read what MinIO left there, so local recordings and files will be lost.
|
|
|
|
|
|
|
|
|
|
To migrate a local environment:
|
|
|
|
|
|
|
|
|
|
1. Stop the stack and remove its containers, including the former `minio` one: `docker compose down --remove-orphans`
|
|
|
|
|
2. Optionally reclaim the space used by MinIO: `rm -rf data/media && make data/media`
|
|
|
|
|
3. In your `env.d/development/*` files, replace `minio:9000` by `garage:9000`, the `meet` / `password` credentials by `meet-access-key` / `meet-secret-access-key`, and add `AWS_S3_REGION_NAME=local` (or delete these files and run `make create-env-files`)
|
|
|
|
|
4. Run `make create-env-files` to generate `env.d/development/garage`, which holds a random RPC secret for Garage.
|
|
|
|
|
5. Rebuild the images, since the summary and agent images now install boto3 instead of minio
|
|
|
|
|
|
|
|
|
|
### Summary service and metadata collector: boto3 replaces the minio client
|
|
|
|
|
|
|
|
|
|
The summary service and the metadata collector agent now talk to S3 through boto3 instead of the minio client, with the same settings.
|
|
|
|
|
Requests are now signed for `AWS_S3_REGION_NAME` as-is. When it is not set, the region is no longer looked up from the bucket: boto3 falls back to `AWS_DEFAULT_REGION`. If you left `AWS_S3_REGION_NAME` unset, set it to your provider's region before upgrading, or providers that check the signing region will reject the transcripts, summaries and meeting metadata uploads, as well as their signed URLs.
|
|
|
|
|
|
|
|
|
|
Also:
|
|
|
|
|
- Signed URLs to transcripts and summaries are now always path-style (`<endpoint>/<bucket>/<key>`), whereas the minio client used virtual-hosted-style URLs
|
|
|
|
|
- The metadata collector now accepts `AWS_S3_ENDPOINT_URL` with or without a scheme, like the summary service: the scheme always follows `AWS_S3_SECURE_ACCESS`.
|
|
|
|
|
|
|
|
|
|
### Helm chart: media services default to Garage
|
|
|
|
|
|
|
|
|
|
The `meet` chart now defaults `serviceMedia.host` and `serviceMediaFiles.host` to `garage.meet.svc.cluster.local`, and the `upstream-vhost` annotation of `ingressMedia` and `ingressMediaFiles` to `garage.meet.svc.cluster.local:9000`. If you relied on the former `minio.meet.svc.cluster.local` defaults, set these values explicitly to your S3 service before upgrading, or recordings and files stop being served under `/media`.
|
|
|
|
|
|
|
|
|
|
## v1.30.0
|
|
|
|
|
|
|
|
|
|
### Removing S3 storage-event webhooks for recordings
|
|
|
|
|
leo