Compare commits

...

156 Commits

Author SHA1 Message Date
Mathieu Velten b8992156da ✨(backend) create LiveKit rooms before handing out join tokens
Create the LiveKit room through the RoomService API before returning a join token, on join, lobby admission, roomkit dial-in and connection tests.

Rooms are only created when missing: LiveKit's CreateRoom overwrites the metadata of an existing room, which would clear the recording state.

This lets LiveKit run with room.auto_create: false, so Meet can share an instance with services that need it to stay secure.

Refs #1209
2026-11-16 16:58:47 +01:00
unteem d06fddab56 📝(doc) create complete documentation website for Meet
Add a documentation site built with Zensical: getting started,
self-hosting with compose and Kubernetes, configuration, user guide,
contributing and reference pages, and every environment variable on
one page, grouped by feature.

Co-authored-by: davd-gzl <60177543+davd-gzl@users.noreply.github.com>
2026-11-16 10:59:49 +01:00
lebaudantoine a3c522b21b ♿️(frontend) put the ProConnect link label inside the link
The ProConnect sign-in link was an empty <a> named only by an
aria-label, its wording living in a CSS background image. RGAA
test 6.2.1 asks for a label between <a> and </a>.

Move the label into visually hidden text inside the link and drop
the aria-label, so the accessible name comes from the content.

Fixes #1898
2026-11-16 00:49:25 +01:00
lebaudantoine 906317d93c ♿️(frontend) use a heading for every connection test card title
Only cards with expandable details had an h3, so the titles of the
other cards were missing from the heading structure.

Wrap the row of non-expandable cards in an h3 too. No visual change.

RGAA 9.1

Fixes #1902
2026-11-16 00:49:25 +01:00
lebaudantoine b5820174a1 ♿️(frontend) show the focus ring on connection test detail cards
The global focus rule overrode the trigger's inset outline offset,
pushing the ring outside the card where overflow: hidden clipped it.

Force the inset offset so the ring stays visible.

RGAA 10.7

Fixes #1905
2026-11-16 00:49:25 +01:00
lebaudantoine 896693c147 📝(docs) invite readers to star the repository
Most people using La Suite Meet never land on GitHub, and those
who do had no prompt to star the project. Stars help other people
and public organisations discover it.

Add a single line at the end of the README introduction, kept
discreet to avoid stacking a second callout next to the Matrix one.
2026-11-14 01:34:08 +01:00
lebaudantoine b6b3ce28db ♿️(frontend) name settings tabs on small screens
Below 800px the settings tabs only render their icon, which left
each tab, and the tab panel it labels, without an accessible name.
Screen reader users could not tell which settings section they
were opening.

Set aria-label on each tab with its existing translated label.
On wide screens it matches the visible text, so nothing changes.

Fixes #1855
2026-11-14 01:05:10 +01:00
lebaudantoine f27f2fb7de ♿️(frontend) raise contrast of inactive intro slider dots
Inactive dots of the home intro slider were 1.57:1 on white, below
the 3:1 RGAA 3.3 asks for, so low-vision users could not tell how
many slides exist.

They are now hollow: a primary.100 fill with a primary.500 outline
at 4.22:1 on white. This passes without darkening the dots so much
that they blend with the active one. Dots grow from 6px to 8px to
keep the outline legible.

Fixes #1851
2026-11-14 01:05:10 +01:00
lebaudantoine 061025b928 ♿️(frontend) structure connection test cards as lists
The step cards of each connection test section are a series of
similar items but were rendered as plain divs, so assistive
technologies could not announce them as a list or give the item
count.

Render each series as a ul with one li per card. The heading and
accordion stay inside the li. No visual change.

Fixes #1903
2026-11-14 01:05:10 +01:00
lebaudantoine 100044eeaa ♿️(frontend) warn before language change in settings
Selecting a language in the settings modal translates the whole
interface immediately. Nothing announced this beforehand, so a
screen reader user could end up in a language they don't read,
with the dialog title already announced in it.

Add a visible description under the "Langue de l'application"
field, linked to the select trigger with aria-describedby, stating
that the change applies to the whole interface on selection.

This satisfies RGAA 7.4 (WCAG 3.2.2 On Input) without adding an
extra confirmation step.

Fixes #1859
2026-11-14 01:05:10 +01:00
lebaudantoine e158b4faaf ♿️(frontend) fix grey text contrast on the connection test page
Zero counters, pending and skipped labels and step summaries used
greys below the 4.5:1 minimum of RGAA 3.2. They now use greyscale.600,
which passes on white, hovered and expanded rows.

Fixes #1897
2026-11-14 01:05:10 +01:00
lebaudantoine 3a1f0a342d ♿️(frontend) mark the language of each option in language selects
Language names are listed in their own language ("English",
"Deutsch", "Nederlands"...), but nothing told assistive technologies
so. Screen readers pronounced them with the rules of the interface
language, which can make them hard to recognise.

Select items accept an optional `lang`, rendered on a span around
the label. useLanguageLabels sets it for every language it returns.

RGAA 8.7

Fixes #1861
2026-11-13 23:38:16 +01:00
lebaudantoine 62571cd9fc ♿️(frontend) declare a background color with the body text color
Text colors were set without a matching background on the document.
With custom browser or system colors, the user's background could
end up behind our text color and make it unreadable.

Set both the default background and text colors on body, so they
are always defined as a pair.

RGAA 10.5

Fixes #1863
2026-11-13 23:38:05 +01:00
lebaudantoine 8fccf46429 ♿️(frontend) give the transcript language button an explicit name
In the transcript panel, the button showing the meeting language
opens the transcription settings, but its accessible name was only
the language itself, e.g. "Français (fr)". Screen reader users had no
way to know it changes the meeting language.

Add an aria-label that keeps the language and states the action. The
visible label is unchanged. Translated in all six locales.

RGAA 7.1

Fixes #1868
2026-11-13 23:37:48 +01:00
lebaudantoine 9481350383 ♿️(frontend) use level 2 headings in the recording side panels
The side panel already exposes its title as a level 1 heading. The
transcript and screen recording panels rendered their intro line as a
second h1, so screen reader users navigating by headings could not
tell the panel title from its subtitle.

Render both intro headings as h2 while keeping the h1 visual style,
so the hierarchy is correct and nothing changes on screen.

RGAA 9.1

Fixes #1882
2026-11-13 23:29:39 +01:00
lebaudantoine e9a58d270b 🚸(frontend) bring raised hands into view in the carousel
A raised hand matters as much as someone speaking, but it went
unnoticed when the tile was scrolled out of the carousel. It is now
brought to the top like a new speaker and stays visible while raised.
2026-11-13 23:26:49 +01:00
lebaudantoine e3351075aa 🚸(frontend) bring new speakers to the top of the carousel
In the focus layout, when someone off screen started speaking, their
tile replaced whichever tile was evicted, often at the bottom of the
column. A screen share that started did the same. Users had to scan
the whole column to find who was talking, and the spot changed every
time.

New speakers now always appear at the top, right below the local
camera and the screen shares, and the other tiles slide down by one.
The most relevant tiles are where the eye already is, and the column
moves in a predictable way.

The ordering still relies on LiveKit's sort and stable update; only
the position of the incoming tile changes. This is the enhancement
#1805 was after.
2026-11-13 23:26:48 +01:00
lebaudantoine 68198e9961 🐛(frontend) promote the active speaker in the carousel layout
Regression: in the focus layout, a participant who started speaking
while their tile was outside the visible part of the carousel was no
longer brought into view.

Cause: 81f23aeb moved useTracks in StageLayout to `updateOnlyOn: []`
so the whole stage stops re-rendering on every ActiveSpeakersChanged.
useVisualStableUpdate only promotes speakers when its host renders, so
it needs something to wake it up. The grid layout got that with
useSpeakerPromotionTrigger in the same commit; the carousel did not,
and nothing else re-renders it on speaker events.

Fix: the carousel now uses the same tripwire. Unlike the grid, which
passes its current page, the carousel renders every tile in a scroll
container, so only the first maxVisibleTiles are passed as visible.

The tripwire also takes the full list of tiles the layout shows and
ignores speakers who have none. In the focus layout the pinned camera
is rendered by the focus view, not the carousel: without this, each
speaker event from that participant would force a render that cannot
promote anyone. The grid passes all its tracks, so its behaviour is
unchanged.

Known limit, not addressed here: when a single tile fits, it stays on
the local camera, which useVisualStableUpdate sorts first, so a remote
speaker cannot be promoted and the tripwire keeps firing for them.

This supersedes #1805, which will be closed. On top of this fix, it
pinned the active speaker to a fixed slot next to the local camera,
first with a 2s hold, a reserved slot and an eligibility check
(867a14d0), then simplified to the last remote speaker with no timer
(378e3d01). That is an enhancement rather than part of the fix, and it
is left out here to keep the regression fix small. It can come back in
a dedicated PR; it would also cover the single-tile case above.
2026-11-13 23:26:48 +01:00
lebaudantoine e3140e0300 🐛(frontend) apply the sans font token on every page
Since routes are lazy loaded, the LiveKit stylesheet only ships
with the room chunk. It was the only rule applying `--fonts-sans`
to the document, so pages outside a room fell back to Panda's
preflight system font stack, ignoring custom CSS themes (e.g.
Marianne in the DINUM image) and accessibility fonts.

Point Panda's `--global-font-body` at `--fonts-sans` so the
document font follows the token regardless of which chunks are
loaded.
2026-11-13 23:26:46 +01:00
lebaudantoine eb345610a7 🐛(backend) allow muting when everyone_can_mute is stored as null
A stored null was read as disabled by CanMuteParticipant, since
`.get(key, True)` only defaults when the key is missing, while the
frontend reads null as enabled. Only an explicit `false` now
disables participant muting.

Fixes #1942
Supersedes #1944
2026-11-13 01:31:33 +01:00
lebaudantoine 48d144877a 🍱(frontend) add Portuguese glyphs to Marianne subsetted fonts
The Marianne subsets were generated with a French-only whitelist, so
most Portuguese accented letters were missing. Words like "não",
"ação" or "país" fell back to the system font for single letters,
which looked broken in the middle of Marianne text.

Regenerate the 12 files from the full Marianne sources tracked in
numerique-gouv/lasuite-landingpage (src/fonts/sources), using the
glyphhanger 5.0.0 command documented there, with these characters
added to the whitelist:

- letters: Á Â Ã Í Ó Õ Ú Ü á ã í ó õ ú ü
- ordinal indicators: º ª
- punctuation: – — ‘

The previous files came from an older whitelist, so this also brings
in the characters added upstream since then (ä ł ń $ ~). No glyph
was removed. Each file grows by roughly 1 KB.
2026-11-13 00:29:07 +01:00
Railton Vasconcelos 5b6ed14a31 🌐(i18n) add Portuguese language support
Add Portuguese (pt / pt-BR) localization across the frontend UI
(all 11 i18next namespaces) and backend Django catalog (pt_BR).

Contributed by the Alan Turing Laboratory (ATLab) at the Federal
University of Ceara (UFC), Brazil.
2026-11-13 00:07:32 +01:00
lebaudantoine 6f8f5d0386 🐛(frontend) accept meeting links with query params in join dialog
Meeting links inserted into events by the Outlook calendar add-in carry
tracking query parameters, e.g. `?from=outlook-addin` or `utm_*`.
Pasting such a link into the "Join a meeting" dialog failed: the
validation regex was anchored on the room id, so any trailing query
string made the link invalid, and the submit handler only stripped the
origin, so the query string would have ended up in the room id.

Parse the input with the URL API in a new `extractRoomId` helper, used
by both validation and submit. It accepts a bare room id or a link on
the current origin (trailing slash allowed), reads the room id from the
pathname only, and returns the query string and fragment separately so
they are kept when redirecting to the room (utm tracking is preserved).
2026-11-12 23:50:05 +01:00
lebaudantoine 25122deba2 🔒️(docker) move frontend to nginx/nginx-unprivileged image
The nginxinc/nginx-unprivileged image is no longer rebuilt and
ships libxslt 1.1.43-r3, affected by CVE-2026-125350,
CVE-2026-87636 and CVE-2026-9947.

Use nginx/nginx-unprivileged in both frontend images. Its
packages are up to date, so drop the manual package upgrades.
2026-11-12 23:29:14 +01:00
briquet 9ede799cb9 🔒️(docker) upgrade musl-utils to fix CVE-2026-107891
Update musl-utils in all alpine images
2026-11-07 00:02:49 +01:00
briquet cc4275c23c 👷(ci) ignore sqlite and zlib CVEs in trivy
Ignore CVE-2026-119374 and CVE-2026-119379 (libsqlite3-0) and
CVE-2026-85091 (zlib1g) until 2026-12-05: Debian trixie ships no
fixed version yet.
2026-11-06 22:14:51 +01:00
briquet d1489f8a61 📌(summary) pin kombu to keep celery workers compatible
Pin kombu to 5.6.2 to avoid problem with redis-py that require
a more recent version of Redis >= 6.X
2026-11-06 22:14:51 +01:00
Roee Sivan c6beb8ed3e ♿️(frontend) close the invite dialog with the Escape key
The "Your meeting is ready" dialog is a react-aria Dialog rendered
without a ModalOverlay, so nothing handled Escape. It stays non-modal
on purpose, so the meeting remains usable while it is open.

Reuse useEscapeToClose, as the side panel does, so Escape only closes
the dialog when focus is inside it and does not take the key from the
chat, the side panel or menus.

The dialog opens on its own when joining, so there is no trigger to
restore focus to. Both the close button and Escape now move focus to
the first control bar button instead of letting it fall back to body.
2026-11-05 22:38:01 +01:00
Florent Chehab 505c55d3b9 📝(changelog) document summary privacy improvements
Record signed URL protection, secret-aware validation errors and safer
logging and Sentry capture under Unreleased.

Document the retention of redacted frame locals and application DEBUG
diagnostics.
2026-11-05 20:18:34 +01:00
Florent Chehab 72d964656c 🔒️(summary) scrub Sentry events and breadcrumbs
Redact signed URLs and remove untrusted exception messages, request
bodies and breadcrumb payloads from Sentry events and transactions.

Preserve stack-frame locals after the existing content scrubber runs.
Cover real HTTP failures, chained exceptions and DEBUG breadcrumbs.
2026-11-05 20:18:34 +01:00
Florent Chehab 58bf9a7d82 🔒️(summary) hide sensitive Celery task details
Publish redacted task argument representations and filter task results
and exception details from INFO-and-above Celery trace logs.

Keep task identity and DEBUG diagnostics available.
2026-11-05 20:18:34 +01:00
Florent Chehab 72af9d629e 🔒️(summary) sanitize analytics client failures
Avoid chaining raw analytics client errors or logging feature-flag
exception messages. Preserve event metadata and feature-flag fallback
behavior.
2026-11-05 20:18:34 +01:00
Florent Chehab 3cd2cb5591 🔒️(summary) sanitize LLM failures and summary progress logs
Raise safe LLM errors for upstream failures and invalid structured
responses without retaining the original exception chain.

Keep generated section titles out of INFO progress logs and preserve
the existing DEBUG diagnostics.
2026-11-05 20:18:34 +01:00
Florent Chehab fcd37b0f26 🔒️(summary) sanitize upstream HTTP failures
Replace raw download, transcription, webhook and Docs exceptions with
safe messages while preserving retryable exception categories.

Retain document IDs and DEBUG responses. Give webhook regression tests
their own tenant settings instead of relying on development tenants.
2026-11-05 20:18:34 +01:00
Florent Chehab b6a8ae7d35 🔒️(summary) clean validation errors at application boundaries
Use cleaned validation errors for task execution, prerun signals,
transcription responses and API results. Share the same cleanup with
FastAPI validation responses while retaining ordinary input values.

Verify secret masking, preserved diagnostics and summary retries.
2026-11-05 20:18:34 +01:00
Florent Chehab 68848c0d6f 🔒️(summary) protect signed URL model fields with SecretStr
Validate signed URLs as secrets and reveal them explicitly for file
access, Celery messages, webhook delivery and authorized API responses.

Cover model representations, nested broker payloads and URL consumers.
2026-11-05 20:18:34 +01:00
Florent Chehab 2ea5c85436 🔒️(summary) add secret-aware validation errors
Preserve Pydantic error categories and diagnostics while masking nested
SecretStr inputs and avoiding retained validator exception objects.

Support custom error codes and safe pickling for Celery.
2026-11-05 20:18:34 +01:00
Florent Chehab 57a4446710 🔒️(summary) redact signed URLs in source logs and analytics
Strip URL credentials, query strings and fragments from file-service
logs and analytics source metadata using one shared helper.

Cover malformed URLs, non-string inputs and signed source URLs.
2026-11-05 20:18:34 +01:00
briquet df723e6a0e 🔒️(agents) upgrade python to 3.14.10 to fix CVE-2026-109518
The python:3.14.8-slim base image ships apt 3.0.3, which is affected by
CVE-2026-109518.
2026-11-05 18:30:51 +01:00
briquet 900ebd3edd 👷(ci) ignore zlib CVE-2026-76844 in trivy
Debian hasn't provided a fix yet
2026-11-05 18:30:51 +01:00
briquet c4fbfdd302 🔒️(backend) refuse unregistered rooms whose slug is a UUID
A registered room's LiveKit room is named after its id, and a room slug
can never be a UUID. A lookup such as "<id>!" does not parse as a UUID,
so it was searched as a slug, found nothing and was treated as an
unregistered room. Its slug, normalized back to the bare id, then got a
token for the registered room without going through the lobby, whenever
unregistered rooms are allowed.

Unregistered rooms whose slug is a UUID now return a 404.
2026-11-05 18:30:51 +01:00
briquet 6f1b9ddba7 🐛(frontend) show join errors instead of silently waiting in the lobby
When joining failed with anything but a 404/410, the lobby started
waiting as if entry had to be requested. Requesting entry now fails
uniformly.
2026-11-05 18:30:51 +01:00
briquet e412dec76f 🔥(backend) drop is_administrable from unregistered room payloads
Registered rooms stopped returning is_administrable in v1.25.0, and
nothing reads it for unregistered rooms either: administrable rooms are
detected from their accesses.

The frontend ApiRoom type drops is_administrable as well, which the API
no longer returns.
2026-11-05 18:30:51 +01:00
briquet 6af43ebf1d 🔒️(frontend) send the display name in the join request body
The room query joins the room, creating it first when missing, and keeps
the response, LiveKit credentials included, in the room cache entry. It
joins again to renew the token once its data is 6 hours old.

Conference and Lobby component were simplified by regrouping custom
hooks, states/refs, memo/callback and mutations.
2026-11-05 18:30:51 +01:00
briquet 4e953da226 🔒️(backend) issue room access tokens via a POST join endpoint
Room access tokens were returned by GET /rooms/{id}/, with the LiveKit
display name passed as a query parameter. We want to leverage Django's CSRF
checks and avoid displaying usernames in access logs.

Tokens are now only minted by POST /rooms/{id}/join/, which reads the
display name from the request body and the livekit information have been
removed where they were not required.

Joining an unregistered room now builds its livekit block with
generate_livekit_config, which mints the same token as the dict it
replaces.

The serializer and the lobby now share LobbyService.can_bypass_lobby to
decide who may enter directly to centralize the logic.
2026-11-05 18:30:51 +01:00
leo f45628d881 ⬆️(dependencies) update python dependencies in summary
Update python dependencies in summary.

Co-Authored-By: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-11-03 20:19:34 +01:00
leo 6fb698a63d ⬆️(dependencies) update python dependencies in agents
Update python dependencies in agents.

Co-Authored-By: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-11-03 20:19:34 +01:00
leo 5887795858 ⬆️(dependencies) update python dependencies in backend
Update python dependencies in backend.

Co-Authored-By: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-11-03 20:19:34 +01:00
leo 21b9b42cb1 👷(ci) update trivyignore
The trivy scan fails on HIGH vulnerability CVE-2026-119373
found in the Debian 13 base images. As it has no fixed version,
add an exception to trivyignore. Also add expiry date for all
exceptions.
2026-11-03 19:41:26 +01:00
briquet 2b9eba72a6 ⬆️(dev) upgrade LiveKit server to v1.13.11 and egress to v1.15.0
Upgrade the local and helm dev stacks
2026-11-03 08:43:25 +01:00
briquet 327f405559 🐛(frontend) show the transcript mic hint when every mic is muted
Since LiveKit Egress v1.13, transcripts no longer go through Chrome:
audio-only egresses always use the SDK source, which only starts on the
first audio packet. A muted microphone sends none, so a transcript
started while every microphone is muted stays "starting" until someone
unmutes.

The hint asking participants to turn on their microphone only showed
when no microphone was published at all, as it counted muted ones. Only
count unmuted microphones for transcripts. Screen recordings still run
in Chrome and keep counting every track.
2026-11-03 08:43:25 +01:00
briquet 35c3491ab2 ✨(frontend) tell participants when a recording is interrupted
The backend now notifies participants with transcriptionInterrupted or
screenRecordingInterrupted when LiveKit Egress cuts a recording short but
keeps what it recorded so far.
2026-11-03 08:43:25 +01:00
briquet 41f3d1def4 ✨(backend) keep recordings cut short by LiveKit egress
Since LiveKit Egress v1.14, an egress cut short still uploads what it
recorded, but Meet either throws it away or saves it silently:
- a transcript that loses its room connection, once the SDK gave up
  reconnecting, ends FAILED with "recording ended early: connection to
  room failed": it was flagged as failed and was never transcribed
- an egress drained because its host ran out of CPU ends COMPLETE with
  the end reason "CPU exhausted": the truncated file was saved without
  telling anyone. If the drain outlasts its grace period, the egress gets
  killed and ends FAILED instead, with the same end reason, and with or
  without its file uploaded.

A new INTERRUPTED worker event is created :
- the recording is saved and sent to external services as usual, and the
participants of an active recording are told that only part of it was
kept.
- A FAILED egress only counts as interrupted when one of its files
has a location, which egress sets once the upload succeeded. Other
failures stay failures, even with an uploaded file.
2026-11-03 08:43:25 +01:00
briquet 22a93947d5 ✨(frontend) add an exponential backoff reconnection policy
When a LiveKit node crashes or Redis stalls, every client loses its signal
connection at the same time. LiveKit's default policy has been jittered
since 2.23.0, but it retries within 500 ms, then again within 450 ms, and
stops after about 45 s of delays, which can be too short for an outage.

Add a reconnection policy with a random exponential backoff. Before its
first attempt, a client waits a random delay up to 1 s by default. That
ceiling doubles after every failed attempt, capped at 10 s, and later
delays fall between half the ceiling and the ceiling. Without that floor,
retries happen at the same time when the service comes back

A client gives up after 3 minutes by default, unless its media still
flows. A client that drops again soon after reconnecting resumes the
backoff one step above where it stopped. The PostHog telemetry now reports how
long a reconnection lasted and when the policy gave up.
2026-11-03 08:43:25 +01:00
briquet b9748983ac ✨(backend) expose livekit reconnect settings in the config
When a LiveKit node crashes or Redis stalls, every client loses its signal
connection at the same time and tries to reconnect at once. The frontend
is about to spread these reconnections with a random exponential backoff.

Expose its parameters under livekit.reconnect in the config endpoint to
let each deployment tune them without rebuilding the frontend.

LIVEKIT_RECONNECT_MAX_DELAY_MS defaults to 10 s: with delays drawn between
half of it and all of it, a client retries every 7.5 s on average, close
to the 7 s of LiveKit's default policy in a long outage.

LIVEKIT_RECONNECT_BACKOFF_ENABLED switches back to LiveKit's default
policy.
2026-11-03 08:43:25 +01:00
briquet f7c3f392ef 🐛(frontend) show a page when the connection ends unexpectedly
When a room ended for a reason Conference did not handle, the user was
left on a dead call screen. This happens when the SDK gives up
reconnecting and when the join itself fails. Since livekit-client 2.22.1
it also happens when the WebSocket upgrade times out during the join,
which 2.21.0 reported as a cancellation and sent to the "you left the
meeting" page.

Send these users to the feedback page with a heading of its own: the
connection was lost if the room had connected, the meeting could not be
joined otherwise. Both keep the buttons to rejoin or go home. A join that
never succeeded leaves no call to rate, so the rating is hidden.

A full reconnection removes every remote participant until it succeeds,
which the idle-disconnect timer took for being alone in the room. Only
run that timer while the room is connected, so a long reconnection does
not end with the user sent away.
2026-11-03 08:43:25 +01:00
briquet 0c357c8b46 ⬆️(frontend) upgrade livekit-client from 2.21.0 to 2.23.0 2026-11-03 08:43:25 +01:00
briquet cae6c19da8 🔖(minor) bump release to 1.37.0 2026-11-01 14:07:10 +01:00
briquet 455daf1e8f ⚡️(docker) build frontend assets natively for arm64 images
Release images were building the JS bundles under QEMU for arm64, which
took most of the 10 to 17 minutes spent on each frontend image on CI.

Since the output is mostly static files, we can use the build platform
for the multi stage build steps of frontend images and share them
between architectures.
2026-10-31 11:41:06 +01:00
briquet 73b182b34a ⬆️(backend) upgrade django-lasuite to v1.0.0
Upgrade django-lasuite from 0.0.29 to 1.0.0.

An inactive token on the external API is now refused with a 401 error
instead of a 400.
2026-10-31 11:22:28 +01:00
briquet 6a1622cd50 🔒️(frontend) keep rooms out of search engine
Room URLs were appearing in search engine results.
The indexing is now restricted  to allow only the landing page.

- Emit a separate `home.html` during the Vite build without a `noindex` tag
- Configure Nginx to serve `home.html` exclusively at `/`
- Serve all other routes with a `noindex` meta tag and an
  `X-Robots-Tag: noindex` header
2026-10-31 11:22:28 +01:00
briquet 56b5a34ec5 ✨(frontend) replace the Crisp chat with the La Suite support form
LaSuite no longer uses Crisp for support.

Users now reach the team through the La Suite support form. It opens
from the in-room "Contact support" menu item and from the main page
as well

The widget is configured with the widget_script_url, widget_api_url and
widget_channel keys that uses shared values with other LaSuite projects
It won't show if the script URL are not configured.
2026-10-29 17:01:06 +01:00
Florent Chehab 815baa73e8 ⬆️(summary) update ffmpeg to 8.1.3-r0
8.1.2 is not available anymore and the image build fails.
2026-10-26 13:28:56 +01:00
briquet 85670a02d5 🔖(patch) bump release to 1.36.3 2026-10-23 21:48:52 +02:00
briquet 21121e8bc1 🔒️(backend) upgrade djangorestframework to 3.18.2
Fix three vulnerabilities in djangorestframework

- CVE-2026-114136: a compressing codec in the Content-Type charset
  lets an unauthenticated body bypass Django's size limit,
  causing memory-amplification denial of service
- CVE-2026-114137: TokenProxy.delete() reports success without deleting
  the token
- CVE-2026-114138: crafted Accept headers make content negotiation burn
  seconds of CPU per request, exhausting workers
2026-10-23 21:46:44 +02:00
briquet 1717c65f2b 🔒️(frontend) upgrade nginx to 1.30.6 to fix CVE-2026-15176
Bump the nginx-unprivileged base image to 1.30.6-alpine3.24, which
fixes a heap overflow when using alias with rewrite, along with
CVE-2026-93479, CVE-2026-95101 and CVE-2026-97629.

https://nginx.org/en/security_advisories.html
2026-10-23 21:46:44 +02:00
briquet fa20d52248 🔒️(all) upgrade brotli to fix CVE-2026-111497
CVE-2026-111497 is an out-of-bounds write in the brotli decoder,
reachable by decompressing crafted brotli data.

- backend: upgrade Brotli to 1.2.1, used by urllib3 and aiohttp to
  decode "Content-Encoding: br" responses
- docker: require brotli-libs >= 1.2.1-r0 in the backend, summary and
  frontend images, the nginx base image ships 1.2.0-r1
- frontend: build the Outlook add-in on Node 22.23.4, Node 20 is EOL
  and will not get the fix

https://www.strix.ai/cve/CVE-2026-111497
2026-10-23 21:46:44 +02:00
briquet 75df71733a 🗃️(backend) add missing editable=False on client_secret_sha256
Migration 0025 declared client_secret_sha256 without editable=False,
while the model field is setting it.
2026-10-21 23:19:05 +02:00
briquet bae6affcba 🔖(minor) bump release to 1.36.2 2026-10-21 21:59:23 +02:00
briquet 708f0d332e 🔒️(frontend) upgrade Node to 22.23.4 and 24.22.1
Pin Node images to the 2026-10-20 security releases
2026-10-21 21:58:23 +02:00
briquet bc1849cb1f 🔖(minor) bump release to 1.35.1 2026-10-21 19:13:00 +02:00
briquet ce29593929 🔒️(backend) upgrade pillow to fix CVE-2026-112403
Upgrade pillow to version 13.0.0 to fix a critical
JPEG decoder vulnerability

https://avd.aquasec.com/nvd/cve-2026-112403
2026-10-21 19:08:40 +02:00
briquet 3bedae346c 🔒️(docker) distrust compromised eMudhra emSign CA roots
Eight eMudhra intermediate CAs were compromised due to weak private
keys, and the emSign Root CA - G3 / ECC Root CA - G3 roots have been
removed from Mozilla and Chrome trust stores.

Update uv, and bump certifi to 2026.10.19 and require
ca-certificates >= 20261020-r0 in Alpine/Debian images

Node.js has not shipped a fixed bundled root store yet.
2026-10-21 19:08:40 +02:00
briquet c03440b92f 🔖(helm) release chart 0.0.29 2026-10-20 15:35:54 +02:00
briquet 1913330ae6 🐛(release) fix prepare-release script on NixOS
The script hardcoded #!/bin/bash, which does not exist on NixOS.
The script was also reformated with 2-space indentation.
2026-10-20 14:45:44 +02:00
Roee Sivan adf9c22a9f ♿️(frontend) announce the microphone turning off on shortcut
The mic shortcut handler treated the value returned by toggle() as a
"did change" flag and skipped the announcement when it was false. In
the room, toggle comes from LiveKit's useTrackToggle, which resolves to
the new enabled state, so turning the mic off returned false and the
screen reader never heard "Microphone turned off".

Make every toggle given to ToggleDevice resolve to the enabled state it
ends in: the camera wrapper now returns LiveKit's result, and the join
screen's toggleTrack, moved to a tested helper, resolves to the initial
state when muting or unmuting fails. ToggleDevice announces only when
that state matches the requested one.
2026-10-20 14:35:14 +02:00
briquet 480be6da6b 🔒️(backend) upgrade aiohttp to fix CVE-2026-111064
Upgrade aiohttp to 3.14.5 in the backend + agents

https://avd.aquasec.com/nvd/cve-2026-111064
2026-10-20 14:05:44 +02:00
briquet 8659182f41 ⚡️(backend) add opt-in psycopg connection pool
Each request opened and closed its own Postgres connection which added a
big overhead. The goal is to add Django's native psycopg pool behind a new
DB_PSYCOPG_POOL_ENABLED settings with explicit min/max size and keepalive.

Each pool lives in one process, and gunicorn's sync workers serve a single
request at a time which means that a given worker won't use more than one
connection. The default pool minimum size is set to 1, which keeps always
one connection open and the maximum size to 3 as headroom for code touching
the database from an extra thread.

Pooled connections can sit idle for hours, so TCP keepalives are enabled
to keep load balancers and NAT from dropping them silently, and each
connection is health checked on checkout so a broken one is replaced
instead of failing the request.
2026-10-20 14:05:44 +02:00
davd-gzl d3302c8644 ♻️(backend) compare LiveKit errors to the SDK not-found code
Use TwirpErrorCode.NOT_FOUND rather than the bare string,
as the SIP service already does.
2026-10-20 12:30:40 +02:00
davd-gzl da3ebc3564 🐛(backend) raise service errors when LiveKit times out
A timed-out call raised a bare TimeoutError past every
service's TwirpError handler, so callers that recover from
a failed LiveKit call, the permission checks and the
webhook handlers among them, failed instead.
2026-10-20 12:30:38 +02:00
davd-gzl 5e2fde5792 🐛(backend) put a timeout on every LiveKit API call
The SDK passes timeout=None to aiohttp on every call, so a
LiveKit that stops answering held a worker until the kernel
gave up. A client middleware now bounds each request, its
answer included, and the client closes the session it is
given, which fixes #1648.
2026-10-20 12:30:32 +02:00
briquet 5c371e8ad8 🔧(dev) enable gitlint as a commit-msg hook in the devenv shell
Commit messages were only checked by the CI lint-git job, therefore
any misformatting was caught only after pushing.
2026-10-19 17:54:47 +02:00
Claude 6711d791cf 🔒️(backend) throttle the start recording endpoint
Each recording start writes a Recording row and spins up a recording
worker, so a user or buggy client hammering the endpoint is costly even
when the calls end in a conflict or a worker failure.

Throttle it per authenticated user, mirroring room creation: a short-term
limit of 10/minute absorbs bursts and a daily cap of 100/day bounds
sustained use. Both are configurable via START_RECORDING_THROTTLE_RATES
and START_RECORDING_DAILY_THROTTLE_RATES.

Only starting a recording is throttled, as it is the costly action.
Stopping a recording only releases resources, so it is left unthrottled
and a throttled user can always stop an ongoing recording.
2026-10-19 17:41:14 +02:00
briquet efaf80c247 🔒️(frontend) upgrade libx11 to fix CVE-2026-88806
Upgrade libx11 to 1.8.14-r0

https://avd.aquasec.com/nvd/2026/cve-2026-88806
2026-10-19 15:25:43 +02:00
briquet 93115f05de ✨(backend) audit Menshen calls and users created from tokens
Register MenshenAuthentication as the menshen_token auth method to record
room operations made with a token exchanged through Menshen as an authentication
acting for its user
2026-10-19 15:25:43 +02:00
briquet ed8799ba06 ♻️(backend) split audit registrations from the action catalogue
core/auditing.py both declared the actions that emitters import and
registered the models and authentication classes: it made it impossible
for authentication class to emit an audit event without an import cycle.

Keep the actions and transit_code_target in core/auditing.py and move the
model and authentication method registrations to core/audit_registry.py, the
module the audit app now autodiscovers.
2026-10-19 15:25:43 +02:00
briquet f1ef84dc9c ✨(backend) audit transit code issuance and exchange
Trace the login flow of the embedded iframe frontend flow.
An application minting a transit code for its delegated user should
logs the transit_code issuance and it's exchange for a user access
token. The transit_code can be identified and with a
SHA-256 to audit eventual replay attacks.
2026-10-19 15:25:43 +02:00
briquet 702d6fefb7 ✨(backend) audit recordings, transcripts and summaries
Emit audit events across the recording lifecycle: recording.start,
recording.stop and recording.delete from the API, recording.end when
LiveKit reports the egress ended, recording.transcript.request when the
backend sends a recording to the summary service, and
recording.transcript.report and recording.summary.report when that
service calls back.

recording.end has an unknown outcome when LiveKit reports an egress
status the backend does not map, and recording.transcript.request names
the summary service as service.target.

Small bugfix: AuditViewMixin keeps a copy of a deleted target, since deleting an
instance clears its primary key.
2026-10-19 15:25:43 +02:00
briquet c87fa7f722 🔒️(backend) audit writes made through the Django admin
Every ModelAdmin now emits an ECS audit event when an object is created,
changed or deleted, and when a bulk action runs. Actions are templated
as admin.<target>.<verb>, after the model name. A signed-in account
without staff access reaching the admin is recorded as a denied
admin.access.

The wiring is a custom AdminSite installed through AdminConfig.default_site:
it mixes the auditing into every admin class at registration, including the
ones Django declares, so a new ModelAdmin is covered without doing anything.
It hangs off log_addition, log_change, log_deletions and get_actions, which
Django calls in every path, rather than off save_model. Deletions noted by
log_deletions are emitted from delete_model and delete_queryset, once their
outcome is known.

Changed field names are always reported; their values only for the
admin_values each model is registered with, and never for anything that
looks like a secret. An account acted upon is reported as user.target:
the target itself when it is a user, else the account its model
registers as user_target, as the user an access grants a role to. The
emitter derives it for every event, so user.provision names the user it
creates as well.
2026-10-19 15:25:43 +02:00
briquet 6826c3d4a6 📝(docs) document audit logging
Describe the audit event shape, the catalogue, how views and other code
emit events, the environment variables configuring them, how the
project registers its actions, models and authentication classes.
2026-10-19 15:25:43 +02:00
briquet bde50506ab ✨(backend) audit external API token and room operations
Emit audit events on the most exposed authentication surface: every
request to the client-credentials token endpoint, issued or refused, as
application.token.issue + provisional user creation + room create,
update, retrieve and list through the delegated rooms API.

Events identify the application by client id, once its credentials are
verified, and the delegated user by id, OIDC sub and email domain
2026-10-19 15:25:43 +02:00
briquet 2c60198184 ✨(backend) add structured audit logging facility
Add a core.audit package emitting one Elastic Common Schema JSON line per
security-relevant action on a dedicated "audit" logger. Only lasuite.*
and entity.target.raw.* extends on ECS core fields. Each event names
the data stream it belongs to (data_stream.*, event.dataset) and carries
a unique event.id.

The audit logs reads the actor, auth method, tenant and network fields from
the request it is given, else from the request being served, which
AuditLogMiddleware keeps in a context variable so that a service needs
no request argument.

A person is identified by primary key, OIDC sub when the account has one
and email domain, with its privileges as user.roles; an internal peer
calling the backend by service.origin.name. The tenant is the
application client id, else that domain. The client IP is DRF's throttle
ident, which now honours a NUM_PROXIES setting.

The middleware also replaces the inbound X-Request-ID with a fresh id,
unless REQUEST_ID_TRUST_HEADER says the ingress overwrites it, and echoes
it in the response and the gunicorn access log. Audit events carry it as
http.request.id, next to the client's user agent.

An action is defined with a dotted name with its default ECS category
and types, validated at import against the types ECS expects in that
category, so a call site only names what was attempted. A category or
types given to audit.log win over them, and a bare dotted name is
accepted too.

 Meet declares all of the events core/auditing.py:
- audit.register lists the fields describing a model as a target, an
  ECS entity.target, and its ECS entity type. Every target carries its
  model name and primary key, so an unregistered one is still
  identified, and a user target its OIDC sub.
- audit.register_auth_method names the lasuite.auth.method of a DRF
  authentication class

AuditViewMixin audits every response of the CRUD actions a view maps in
audit_actions, and of the extra actions naming theirs with
@action(audit_action=...), from finalize_response: the outcome, reason
and status come from the response. An exception DRF does not handle is recorded
as an internal error before it propagates. The core.audit app also
records Django's login, failed login and logout signals.
2026-10-19 15:25:43 +02:00
leo dce67e37f8 ✨(backend) add Menshen token-exchange authentication to external API
Menshen is La Suite's OAuth 2.0 token exchange server (RFC 8693): another
service exchanges its user's access token for a token targeting Meet, then
calls the external API on behalf of that user. Tokens are validated by
introspection (RFC 7662). Menshen only reports a token as active when Meet
is among its audiences.

Add Menshen auth to the external API. Only activate it for room creation
scope (other scopes may be added later). If a user doesn't exist for the
provided sub,  create it, unless the provided email is already associated
to a an existing account.

This PR does not implement fallback to email to automatically create
user when no sub or an invalid sub is passed and email is provided, when
OIDC_FALLBACK_TO_EMAIL_FOR_IDENTIFICATION=True.
2026-10-16 08:33:46 +02:00
lebaudantoine ab6e58ecae ✨(all) allow any authenticated user to start a recording
Any authenticated participant can now start a recording on trusted
and public rooms. This is essential, requested by many users, and
should encourage people to authenticate on public rooms. It also
means the starter may hold no role on the room, so who gets access
to the recording has to be decided explicitly.

The part open to discussion is the recording access: who should be
owner/admin on the recording. This commit picks the simplest
design:

* The room's owners and administrators get an `OWNER`
  `RecordingAccess`: they can retrieve, download, stop and delete
  the recording.
* The starter gets a `MEMBER` `RecordingAccess`, unless they already
  own or administer the room, in which case they get `OWNER`. A
  member can retrieve and download the recording but cannot delete
  it: deletion is irreversible and affects everyone with access, so
  it stays with the people responsible for the room.
* Everyone with an access, members included, receives the
  "recording ready" email.
* Room roles are copied when the recording starts: later changes
  to the room's accesses do not affect existing recordings.

The people responsible for a meeting should control its recording
and transcript, and whoever initiated it should be able to access
it on their own. The starter owns the output and is responsible for
sharing it with their colleagues.

Recording members could not retrieve a recording before this
commit. No code path created such accesses until now, but one added
manually through the admin now grants read access.

One constraint is respected: the summary service creates a doc,
and the docs API can only attribute it to a single owner. The
summary therefore goes to the oldest access, and the starter's
access is created before the room owners/admins ones, so the
starter receives it. The lookup does not filter on role, since the
starter may only be a member. The previous lookup took `.first()`
with the default newest-first ordering, which with several owners
would have picked a room admin.

Alternatives considered:

* Granting access to every participant allowed to record, or to
  those present when the recording starts: it requires listing
  participants from LiveKit and creating an access for each, and
  widens access by default, for a need no user has expressed.
* A `creator` attribute on the recording row: it only adds a
  migration without adding value to access control, so it was
  dropped.
* Restricting access to the link owner even when someone else
  starts the recording: some organizations may want this for
  security reasons, but it is YAGNI until a few large clients ask
  for it.

I think we should contribute to Docs' api to allow sharing the
transcription document with several users.
2026-10-15 09:55:57 +02:00
briquet 9bc712009a 🐛(backend) lock rooms while updating them
Before this commit, a room update and a soft deletion racing each other
could leave the room active.

Both `perform_update`s now re-read the room with `SELECT ... FOR UPDATE`
inside a transaction to avoid this race condition.
2026-10-15 00:42:32 +02:00
briquet 44f598a672 ⬆️(backend) upgrade pylint to 4.1.3
pylint was pinned below 4.0 because pylint-django used to require it.
pylint-django 2.8.0 accepts pylint 4.

pylint 3.x kept too-many-lines pragma line numbers across modules: a C0302
disable in one file could make the check report on the wrong line
in another and fail depending on how files were spread across jobs.
pylint 4.1 resets them per module.

cf https://github.com/pylint-dev/pylint/pull/11191
2026-10-15 00:42:32 +02:00
briquet 10437d6ae1 ✨(backend) purge soft-deleted rooms after a retention period
Add a ROOM_DELETED_RETENTION_DAYS setting, unset by default. The
purge_inactive_rooms command now also deletes rooms soft deleted more
than that many days ago, whether they are inactive or not. Inactive
soft-deleted rooms are now purged under ROOM_INACTIVITY_DELETION_DAYS
too. As for inactive rooms, a room holding a saved recording that has
not expired yet is kept.
2026-10-15 00:42:32 +02:00
leo 44bfef69ca ✨(rooms) soft delete rooms from internal and external API
Before this commit:
1. Rooms could be hard-deleted from the internal API (unused by the
   frontend).
2. The external API had no way to delete a room.
3. The admin could hard-delete rooms.

What this commit does:
1. Add a `deleted_at` field to Room. `Room.objects` hides soft-deleted
   rooms; `all_objects` stays the default manager so deleted rooms keep
   reserving their slug and PIN code.
2. Soft delete rooms from the internal API (replacing hard delete) and
   the external API (new DELETE, owner only, `rooms:delete` scope). The
   LiveKit room is closed and its participants disconnected; if closing
   fails, the soft delete is rolled back and an error is returned.
3. Answer 410 Gone on detail operations on a deleted room (after
   permission checks). Its can still be read but not modified.
4. Close LiveKit rooms recreated after deletion by participants still
   holding a valid token (room_started webhook).
5. Frontend: participants in the call land on the feedback page without
   the rejoin button, lobby participants see a "meeting deleted" screen,
   and opening the link shows an error instead of recreating the room.

Untouched by this commit:
- The admin still hard-deletes rooms, without closing the LiveKit room,
  and lists soft-deleted rooms alongside active ones.
- Purging soft-deleted rooms (hard deletion) is not handled.
- Scheduled deletion is not handled.
2026-10-15 00:42:32 +02:00
Roee Sivan eb422309b9 ✨(backend) allow static feature flags without an analytics backend
Feature flags are read from the analytics backend. Without one,
NoOpAnalytics returned no flag, so "summary-enabled" was always off and
a self-hosted instance could not get automatic summaries without PostHog.

NoOpAnalytics now accepts a static "feature_flags" mapping through the
existing ANALYTICS_BACKEND_SETTINGS, and get_analytics() passes the
settings to it. Nothing changes when no flag is declared.

Fixes #1610
2026-10-14 00:19:55 +02:00
leo 4854fc0c13 🔒️(devex) bind ports in compose.yaml to localhost
Some containers were being exposed to local networks. Bind them
to localhost, to tighten security. Don't apply this binding to
LiveKit (exposed on 7880), as we access it using 127.0.0.1.nip.io:7880.
2026-10-13 18:21:04 +02:00
lebaudantoine d930fa1ba6 ⚡️(backend) add UPPER(email) index for case-insensitive user lookups
Case-insensitive user lookups during token issuance currently take
around 100 ms in production, accounting for roughly a third of the
total 300 ms token request trace.

Add an `UPPER(email)` index on the user table so these lookups can
use the index instead of scanning, cutting the dominant cost on
the token issuance path.
2026-10-13 15:20:04 +02:00
lebaudantoine 6f1414b34e 🔖(minor) bump release to 1.35.0 2026-10-13 09:34:46 +02:00
lebaudantoine 0194f7f3f3 ⚡️(backend) send recording notification emails from a Celery task
Emails were rendered and sent inline in the LiveKit webhook, so a
slow SMTP server blocked the request and a transient failure lost
the email. Delivery now runs in a worker, with retries and backoff.

The task is generic (template, subject, recipients, context,
language) so other emails can reuse it. The subject is translated
in the worker, and dates are formatted per owner before queuing,
so the arguments stay JSON-serializable.

Without Celery, the task still runs synchronously. Success now
means "queued", not "delivered".
2026-10-11 23:37:00 +02:00
Roee Sivan 0bde103911 🔧(project) silence gitlint regex-style deprecation warning
gitlint prints a warning for each ignore-by-title rule because it will switch
its regexes from match (start of the string) to search (anywhere) semantics.

Both ignore-by-title regexes are already anchored with ^, so they match the
same titles either way. Setting regex-style-search opts in to the new behavior
now and removes the warning.

Fixes #96
2026-10-11 23:34:02 +02:00
lebaudantoine c7c41abcb5 ✨(frontend) let users pick the recording encoding
Add a Recording tab to the settings dialog with two selectors, a
content profile and a resolution, building on the per-recording
encoding API.

The goal is to let an instance default to a cheaper profile and
resolution to save egress CPU, while users who really need a smooth
HD recording can still opt in. Most users only need a recording of
acceptable quality, so the default stays cheap and configuring it is
optional.

Profiles are labelled by content ("Talking heads", "Presentations and
text", ...) rather than by fps or bitrate: users know what they are
about to record, not which encoder settings fit it. Each profile shows
a one-line description of its trade-off, so picking one requires no
technical knowledge.

The panel gets a third row, matching the meeting language row of the
transcript panel. It is a shortcut to the settings, without adding
mental load about how to configure a recording. It reads as a short
statement with a trailing "Change" link, like the informational rows
above it, and stays on a single line in every locale: the statement
truncates if a translation gets too long, the link never wraps.

The selected options are intentionally not shown in the panel.
Several users can access it, and each would see their own local
configuration while the running recording may use another user's
encoding, which would be misleading. The issue is milder in the
settings tab, which is frozen while a recording is starting or in
progress.

The selectors are disabled from the moment a start request is sent
until the recording is saved, for both screen recordings and
transcripts. Settings are sent once, when the recording starts, so
changing them afterwards would have no effect and suggest otherwise.

Choices are persisted in localStorage to keep things simple,
consistent with the meeting language, which is already stored
client-side.

The backend now exposes the available resolutions and profiles, and
their defaults, in the frontend configuration, so the UI follows
whatever the operator configures instead of hardcoding values. Stored
choices are checked against it before being sent: a profile removed by
the operator falls back to the instance default instead of being
rejected by the API. No encoding is sent when per-recording encoding
is disabled, as the backend would reject it. Operator-defined values
without a translation are shown by their raw key.

Alternatives considered:

- Storing the preference in room metadata: it would turn a pre-start,
  personal choice into shared editable state, requiring a write
  endpoint, permission checks and handling of concurrent edits.
- Notifying participants of the chosen encoding: notifications are
  one-off, so users who join or reload after the recording started
  would miss them, and the information is noise for most participants.

Next steps:

This is a deliberately small first iteration, meant to deliver most
of the value and evolve with feedback and usage. Possible next steps:
- persist the preferences in the backend instead of localStorage
- store the encoding chosen for a recording on the room (or on a
  session, if such a model is introduced) and read it from there
  rather than from user settings, so every user sees the same value
2026-10-11 23:02:57 +02:00
Roee Sivan 531774fbda 🐛(frontend) keep the admin panel in place when changing a setting
React Aria renders the radio and switch inputs visually hidden and
absolutely positioned. Their labels were not positioned, so in the
side panel the inputs were anchored to the aside and did not scroll
with its content. Focusing one made Chrome scroll the aside, which
has no scrollbar, hiding the panel content.

Position the labels so each hidden input stays inside its control.
2026-10-11 16:08:25 +02:00
Ovgodd 86d97b427c 🐛(frontend) play the speaker test when no output is picked
The speaker test called setSinkId('default'). Firefox rejects it
and playback stopped. Skip that id and play on the system output.
2026-10-11 00:16:47 +02:00
Ovgodd b0bb5bc61b 🐛(frontend) omit the default speaker id sent to LiveKit
Firefox rejects setSinkId('default') when a remote audio track
is attached. Omit that id and only send a real device id.
2026-10-11 00:16:47 +02:00
Ovgodd 3773e43d93 ♿️(frontend) show a visible focus outline on menu items
Keyboard focus was cleared with outline:none.
2026-10-09 18:13:14 +02:00
lebaudantoine 0d79e6418a 📝(doc) update the CHANGELOG
Update the CHANGELOG with the entries for the recent
changes landed on the project.
2026-10-09 17:37:15 +02:00
lebaudantoine 811540c85f 🔒️(frontend) upgrade tiff to fix CVE-2026-4775
Trivy flags tiff 4.7.1-r0 (HIGH) in the nginx alpine 3.24 base
of the frontend images. Force the upgrade to 4.7.2-r0.
2026-10-09 17:37:15 +02:00
lebaudantoine cee2109726 🐛(backend) use the configured token type in BaseJWTAuthentication
authenticate and authenticate_header hardcoded "Bearer" instead of
using the token type the backend is configured with. Setting
APPLICATION_JWT_TOKEN_TYPE, ADDONS_TOKEN_TYPE or USER_ACCESS_TOKEN_TYPE
to anything else made every token be ignored, since the Authorization
scheme never matched.

Store the token type on the backend and use it both to match the
Authorization header scheme (case-insensitively) and as the
WWW-Authenticate scheme.
2026-10-09 17:37:15 +02:00
lebaudantoine 7fa9c3fa4f ♻️(backend) share the user access token test helper
generate_user_access_token was copy-pasted in seven test modules
(user access token authentication, and rooms create, list, retrieve,
update, participants management, rename/toggle and subtitle).

Extract it into core.tests.utils and reuse it everywhere. The shared
version keeps the optional application and claim overrides from the
authentication tests, and reads the token type claim from
USER_ACCESS_TOKEN_TYPE_CLAIM instead of hardcoding it.
2026-10-09 17:37:15 +02:00
lebaudantoine 191e6d49d8 🔒️(backend) sign lobby participant id
The participant id returned by request-entry was the raw LiveKit UUID,
so anyone knowing it could poll the lobby and obtain the admitted
participant's LiveKit token.

Return the id signed with SECRET_KEY under a lobby-specific salt, and
reject unsigned, tampered or foreign-signed ids with a 400. The raw
UUID is still used internally for the cache and LiveKit identity.
2026-10-09 17:37:15 +02:00
lebaudantoine 5867e079c6 🔒️(frontend) restrict transit_code exchange to embedded context
Only run the transit_code exchange flow when the app is loaded in an
embedded context (i.e. inside an iframe).

Combined with the CSP rules that will restrict which origins are
allowed to embed the app, this gives us a client-side lever to
control which integrations can actually use this authentication
path.
2026-10-09 17:37:15 +02:00
lebaudantoine 96b28da7be 🔒️(backend) bind accepted lobby entries to the current username
Bind an accepted lobby entry to the username the participant had at
the moment of acceptance.

This prevents a participant, once accepted, from changing their
display name and reusing the same lobby grant to enter the room
under a different identity.
2026-10-09 17:37:15 +02:00
lebaudantoine 84450b6f3a 🔥(frontend) remove forgotten console.log calls
Drop leftover `console.log` calls that were accidentally left in the
frontend code and add noise to the browser console.
2026-10-09 17:37:15 +02:00
lebaudantoine 10ac8925fb ♻️(all) stop relying on cookies for the lobby flow
The lobby system relied on cookies to identify the participant
across the wait/enter cycle, which does not work in an iframe
context where our cookies are dropped.

Simplify the lobby behavior:

* The POST request that enters the lobby now returns the
  participant id in the response.
* The frontend passes that id back on subsequent requests to keep a
  sticky session while trying to enter the room.

This moves a bit more logic to the frontend but should be a
transparent refactoring, without decreasing the security of the
lobby flow.
2026-10-09 17:37:15 +02:00
lebaudantoine c2007929f4 🩹(frontend) unblock virtual background loading under bearer auth
Moving off cookie-based authentication surfaced several hard
issues, especially around loading virtual backgrounds: requests
used to be sent with cookies automatically, which trivially
authenticated those loads. With bearer tokens, those requests need
to be authenticated explicitly.

The situation is made harder by the fact that, when the custom
virtual background was introduced, some of the loading was done as
module-level, blocking imports that are not handled by React and
therefore live outside the normal auth flow.

Ship a functional patch to unblock third parties currently waiting
on this integration. The virtual background loading path should
definitely be refactored and simplified in a follow-up.
2026-10-09 17:37:15 +02:00
lebaudantoine ddf19deb82 ✨(frontend) support alternative auth via URL fragment
Wire the frontend to the backend's token exchange flow: when the
expected URL fragment is present, gate the app loading on exchanging
that fragment for a proper access token, which is then used to
interact with the API.

When no such fragment is present, the code path is a no-op and
should have minimal impact on load performance.
2026-10-09 17:37:15 +02:00
lebaudantoine 81876a10d4 ♻️(backend) use a dedicated auth scheme for LiveKit token auth
We now use `Authorization: Bearer <token>` to authenticate users
from the token exchange flow (used for iframe embeds).

Until now, the `Bearer` scheme was also reused for the alternative
LiveKit authentication, where a client presents its LiveKit token
issued by the backend to prove room membership on actions open to
any room participant. Sharing the scheme between the two flows is
not viable anymore.

Switch the LiveKit token authentication to a dedicated
`Authorization` scheme, so `Bearer` stays reserved for the iframe /
token-exchange flow.

Follow-up: a broader effort should look into harmonizing and
hardening the backend authentication stack of the app.
2026-10-09 17:37:15 +02:00
lebaudantoine f123c79741 ✨(backend) introduce a token exchange endpoint for iframe embeds
Some integrators render our videoconference inside an iframe, where
our cookie-based authentication does not work: our cookies are
SameSite=Lax/Strict, so the iframe drops them.

We looked at what Jitsi offers: a shared secret used to sign JWTs
that authenticate users coming from external services. Since we
already expose an external API where third parties authenticate as
a given user, it was simpler for us to add an exchange mechanism on
top of that.

Flow:

* Through the external API, mint a short-lived, single-use exchange
  code for a user.
* The third party hands that code to the frontend as a URL fragment.
* The frontend exchanges the code for a longer-lived JWT that can be
  used to query the regular API viewsets.

Known limitations and follow-ups:

* At some point it would be nice to shorten the JWT lifetime and
  add a refresh mechanism. This will be handled in a follow-up PR
  when actually needed.
* CSP rules to control which origins are allowed to embed the app
  in an iframe still need to be added.
* This alternative authentication cannot easily be scoped to a
  subset of endpoints without adding a lot of complexity, so it is
  accepted globally on the API for now.
2026-10-09 17:37:15 +02:00
lebaudantoine deb1ef9ed6 ⚡️(backend) reduce domain queries on the application token endpoint
Load allowed domains once and compare the lowercased email domain
in Python. For restricted applications with an existing user,
this reduces successful token requests from four queries to three.

Keep domain loading after credential validation so rejected
credentials require only the application lookup.

Add endpoint query-count tests for restricted and unrestricted
successes and invalid credentials.
2026-10-07 19:06:05 +02:00
lebaudantoine 080c347129 🔒️(backend) prevent editing client id and secret in Django admin
The client id and client secret are auto-generated with high entropy
when an application is created. Allowing them to be edited from the
Django admin let any administrator replace them with a short or
weak value, undermining that guarantee.

Make both fields read-only in the admin so they can only be
regenerated through the intended flow.
2026-10-07 18:09:30 +02:00
lebaudantoine 0450c74f53 ⚡️(backend) hash application secrets with SHA-256
Application token authentication currently uses Django's default
password hasher. On our production hardware, token requests take
at least ~500 ms. Authentication happens per user of each
application, so this cost accumulates across frequently used
integrations.

Password hashers deliberately make guessing expensive to protect
human-chosen passwords after a database leak. Our application
secrets are generated server-side using a cryptographically secure
random generator, with a default length of 128 alphanumeric
characters. Guessing these secrets is already computationally
infeasible, making password stretching an unnecessary CPU cost.

Use salted SHA-256 for application secrets while retaining
constant-time comparison, and keep user password hashing
unchanged. Existing secrets migrate after successful verification
without requiring key rotation. Conditional updates prevent
migration from overwriting a concurrent rotation.

Store the new hash in `client_secret_sha256` while preserving the
original Django hash in `client_secret`. New applications populate
both fields, allowing the previous release to authenticate both
existing and newly created applications if we need to roll back.

Once every application has migrated and the rollback window has
closed, complete the migration by removing the legacy verification
code and `client_secret` field.

This assumes securely generated, high-entropy secrets. Deployments
that reduce `APPLICATION_CLIENT_SECRET_LENGTH` or supply
predictable secrets lose the offline guessing protection that the
previous slow hasher provided.
2026-10-07 18:09:30 +02:00
briquet 2ac457c43e 🔖(minor) bump release to 1.34.0 2026-10-07 12:50:40 +02:00
lebaudantoine e9b523b522 📝(docs) document Brevo marketing migration in UPGRADE.md
Explain the switch to django-lasuite marketing: removed BREVO_*
and MARKETING_SERVICE_CLASS settings, new LASUITE_MARKETING_BACKEND
and LASUITE_MARKETING_PARAMETERS variables, dummy backend default,
and the now-required Celery worker.
2026-10-07 12:16:26 +02:00
lebaudantoine 70d348337e 📝(docs) bump UPGRADE.md after v1.33 release
The `Unreleased` section of `UPGRADE.md` was not bumped when v1.33
was released, so follow-up changes landed under the wrong heading.

Reorganize the file so v1.33 is properly closed and a fresh
`Unreleased` section is opened on top.
2026-10-07 12:16:26 +02:00
lebaudantoine 258722adfd ⏪️(docs) revert styling on heartbeat and lbheartbeat probe in CHANGELOG
Revert the formatting changes applied to the heartbeat and
lbheartbeat probe entries in the CHANGELOG, as the previous styling
was intentional.
2026-10-07 11:49:23 +02:00
lebaudantoine 0a6724e7ad 🔧(compose) make the LiveKit agents opt-in in the local dev stack
`make run` no longer starts the metadata collector and the
multi-user transcriber. On my machine, this saves about 400 MB
of RAM and almost 2% CPU, out of the 11% the stack uses.
Start them with `make run-agents` when needed.

Disable `METADATA_COLLECTOR_ENABLED` by default in `common.dist` so
the backend does not dispatch jobs to an agent that is not running,
and document how to enable each agent in `developping_locally.md`.
2026-10-06 22:56:57 +02:00
lebaudantoine c1c2d93932 🔧(compose) share the backend redis with the summary stack
The summary settings already default to the `redis` host, so
`redis-summary` was unused. Remove it and depend on `redis`.

Pin the summary Celery and task tracker URLs to DB 2 in
`summary.dist` to isolate them from LiveKit and the backend
Celery broker (DB 0) and the Django cache (DB 1).
2026-10-06 17:26:26 +02:00
lebaudantoine 9efb9577c4 ♻️(tilt) use the helm dev-backend chart
Use the shared helm `dev-backend` chart to deploy the backend in
the Tilt dev stack, instead of maintaining our own copy.

The goal is to share more common pieces of the dev experience and
dev stack across projects, so we do not maintain N different
versions of similar setups.

The only adjustment needed was to backport Garage into the shared
chart.

Originally started by @rouja.
2026-10-06 14:07:23 +02:00
Ovgodd 2137c6b444 🐛(frontend) let panel shortcuts close panels opened from a menu
allow menu-invoked panels to be closed by panel shortcuts
2026-10-05 15:11:04 +02:00
Ovgodd aa01733f6b ♿️(frontend) make participant pagination readable and keyboard reachable
Improves PaginationControl: clearer structure, keyboard nav, a11y improved.
The main room and the picture-in-picture window share this control.
Ctrl+Shift+G focuses the pagination.
2026-10-05 15:11:04 +02:00
lebaudantoine 03db669e51 🔒️(ci) set persist-credentials: false on actions/checkout
By default, `actions/checkout` saves the job's auth token
(`GITHUB_TOKEN` or the provided PAT) in the local git config so
later steps can run authenticated git commands. That token then
stays on disk for the rest of the job, where it can leak:

* If an artifact upload includes the checkout directory, the token
  is packaged with it and anyone with artifact access can extract
  it. On public repos that is anyone, and the token can be used
  while the job is still running ("ArtiPACKED", flagged by
  `zizmor` as `artipacked`).
* Any later step, third-party action, or build dependency can read
  the token from the git config, which widens the impact of a
  supply-chain compromise.

None of our workflows need authenticated git after checkout, so
disable credential persistence. If a step needs to push in
2026-10-05 12:41:38 +02:00
davd-gzl 97a73bf4f2 🔧(frontend) rename the make target to test-frontend
The frontend test target now sits beside test-back and
test-summary and follows their naming.
2026-10-05 12:41:38 +02:00
davd-gzl 267a2265d9 🔧(frontend) give vitest its own config and a make target
A separate vitest.config.ts keeps the tests off the build
plugins and the mediapipe version check in vite.config.ts.
make test now runs the frontend tests after the backend ones,
and test-front runs on Node 24, the current LTS.
2026-10-05 12:41:38 +02:00
davd-gzl 14507d57a9 ✅(frontend) add vitest so the frontend can carry unit tests
Add vitest as a dev dependency, a test script that runs panda
codegen first, and a test-front job, so the frontend can carry
unit tests. One test covers normalizeRoomId, a plain function,
so no DOM library comes with it.
2026-10-05 12:41:38 +02:00
davd-gzl c075db25a4 🐛(frontend) honour Keep hand raised when picture-in-picture is open
The hand button owns the lower-hand timer and the toast, and the
picture-in-picture window draws a second copy of that button, so two
offers go up and dismissing one leaves the other to lower the hand.
Move the watching into a component rendered once beside the room.
2026-10-04 23:21:31 +02:00
Rishi Gupta c0dfd88776 ♿️(frontend) expose loading state to assistive technology
Surface the page's loading state to assistive technology, so screen
readers can announce that the page is still loading instead of
reading a partially rendered state as if it were complete.
2026-10-04 22:58:21 +02:00
Rishi Gupta 94d2b80c17 ✏️(docs) fix README wording and typos
Address review feedback from #1 by fixing wording issues and typos
across the README.
2026-10-04 22:58:21 +02:00
KusalPabasara bd2dfcae80 ✨(helm) add envFrom support to chart
Allow every chart workload to import environment variables from ConfigMaps.

Keep existing empty defaults for backward compatibility.
2026-10-04 22:34:31 +02:00
lebaudantoine 0b4a83c92e 🐛(brevo) use django-lasuite for marketing management
When the user is updated, their lists on Brevo are overwritten with
the new value: this removes lists set by other products.

Switch to the common lib implementation from `django-lasuite`,
which manages this correctly.

This change was initially proposed by @qbey, but at the time our
deployment did not have a Celery worker running alongside the
backend. Since then, a Celery worker has been deployed, so the
switch to the common lib approach is now safe to adopt.
2026-10-04 22:10:16 +02:00
lebaudantoine 9187173cae ✨(frontend) warn users when the connection falls back to TURN
Highlight in the connection test when the user is connecting
through a TURN relay, especially over TLS or TCP. This usually
indicates that some network configuration is required on their
side, and gives them a concrete signal to pass to their IT team.

Suggested by a technical user, this is a first step toward making
users more autonomous when troubleshooting access to the tool.

Follow-up: show a similar warning in-product when we detect a
mid-meeting fallback to TURN/TLS. A one-time hint for first-time
users would likely be enough.
2026-10-03 23:36:42 +02:00
kaelvar 364bbf4f0b ✨(frontend) let signed-out visitors start a meeting
The home page only offers meeting creation to authenticated users, while the
backend already serves ephemeral rooms to anonymous visitors when
ALLOW_UNREGISTERED_ROOMS is enabled (the flag is checked in the room retrieve
view, not in the create one).

Expose the flag in the frontend configuration and, when it is on, show the
existing "Create a meeting" button to signed-out visitors. It navigates to a
freshly generated room id rather than calling POST /rooms/, which stays
reserved for registered rooms and for authenticated users.

The invite dialog opens for such a creator when the room is unregistered
(null id) and the navigation carries `create`. The `mode` computed in Room
is left untouched, so permissions and the join screen behave as before.

The home buttons row now wraps: signed-out visitors can see three controls
(create, join, login), and at the xsm breakpoint the fixed-width ProConnect
button leaves too little room for the other two.
2026-10-02 19:06:02 +02:00
lebaudantoine a6a12ef586 🐛(frontend) hide tooltips until they have a computed placement
A React Aria overlay is rendered at `top: 0; left: 0` until
`useOverlayPosition` computes its position, and `data-placement` is
only set once that succeeds. When the pointer moves quickly between
triggers, a closing tooltip can mount for its exit animation without
ever being positioned, React Aria does not retry, so it stays
stuck in the top-left corner.

Hide tooltips until they have a `data-placement` set, so unpositioned
tooltips never flash in the corner. Use `visibility` rather than
`display: none`, so the element stays measurable for the positioning
pass.
2026-10-02 18:19:43 +02:00
snyk-bot 2622d89f63 ⬆️(frontend) upgrade react-aria dependencies
Snyk has created this PR to upgrade react-stately from 3.48.0 to 3.49.0.
I had to bump react-aria@3.51.0 react-aria-components@1.20.0
2026-10-02 18:19:43 +02:00
lebaudantoine f2d50770cf 🔧(summary) add setting to control Sentry traces sampling rate
Replace the deprecated `enable_tracing=True` with `traces_sample_rate`,
read from a new `sentry_traces_sample_rate` setting (default 0.1,
validated to the 0.0–1.0 range).

Previously, tracing sampled 100% of transactions, which is costly and
unnecessary in production. The rate can now be tuned per environment
without a code change.
2026-10-02 17:41:02 +02:00
lebaudantoine 11e8470aa5 🔒️(summary) redact meeting content from Sentry events
Sentry attaches stack frame locals to its events. When storing a
transcript in S3 failed, the full transcript held in `data` and
`transcript` was sent to Sentry.

Keep locals for debugging, but scrub variables and nested dict keys
known to hold transcripts, summaries, LLM prompts, participants'
personal data or pre-signed URLs. Share the Sentry init between the
API and the Celery worker, and never send request bodies.
2026-10-02 17:41:02 +02:00
lebaudantoine 3bf78f0f5b 🐛(summary) disable default S3 checksums for GCS-compatible storage
Since boto3/botocore 1.36, the S3 client computes CRC32 checksums on
uploads by default (request_checksum_calculation="when_supported").
PutObject requests are then sent with aws-chunked encoding, a trailing
x-amz-checksum-crc32 header and a STREAMING-UNSIGNED-PAYLOAD-TRAILER
content hash.

Our production storage (S3NS, storage.s3nsapis.fr) is built on Google
Cloud Storage and exposes it through GCS's S3-compatible XML API, which
does not support these flexible checksums. It rejects the request with
a 403 SignatureDoesNotMatch ("Invalid argument"), so storing transcripts
failed in the Celery worker. Garage, used locally, supports them, which
is why the issue only appeared in production after switching the
client to boto3.

Add aws_request_checksum_calculation and
aws_response_checksum_validation settings, defaulting to
"when_required", and pass them to the botocore Config of the summary S3
client and the backend S3 client. Checksums are then only sent for
operations that require them, restoring the pre-1.36 behavior.
2026-10-02 17:41:02 +02:00
lebaudantoine ddd5e3fce1 ✏️(ci) fix a codespell in env variable
Minor typo introduced by the recording configurations.
2026-10-02 17:35:32 +02:00
lebaudantoine 5a9e1cb012 🔒️(frontend) upgrade pcre2 to fix CVE-2026-103111
The nginx-unprivileged:1.30.4-alpine3.24 base image ships
pcre2 10.48-r0, which is affected by CVE-2026-103111 (HIGH,
out-of-bounds write via crafted regular expression). No newer
base image tag is available yet.

Upgrade pcre2 from the Alpine v3.24 repository with a minimum
version constraint (>=10.49-r0) so the build fails instead of
silently shipping a vulnerable version if the fix is unavailable.
2026-10-02 17:35:32 +02:00
lebaudantoine c49cee3ab4 🧑‍💻(devex) fix local recording downloads
Recordings were failing to download in the local stack because of
several small issues stacked together:

* nginx: add a `/media/recordings/` location that authorizes
  against `recordings/media-auth/`. Before, every media request
  went to `files/media-auth/`, which returned 403 for recording
  paths.
* nginx: call `proxy_hide_header Content-Disposition` before
  `add_header Content-Disposition "attachment"`. Garage stored the
  header as `inline`, which combined with nginx's value into
  `inline, attachment` and broke browser downloads.
* frontend: `mediaUrl()` now uses the frontend origin, so
  recording links go through the Vite `/media` proxy instead of
  hitting Django directly on `:8071`.
* frontend: include the file extension in the download filename.

co-author: cameldev
2026-10-02 17:35:32 +02:00
lebaudantoine bbc30de490 ⚡️(devx) switch devstack to node:22-alpine
The devstack was pulling the full `node:22` image, around 1.6 GB.
Switch to `node:22-alpine`, which is much smaller, to speed up the
devstack bootstrap time and reduce disk usage.
2026-10-02 15:59:04 +02:00
lebaudantoine 14b3395e1c ⚡️(devx) use a single Redis image version in the devstack
The devstack was pulling two different versions of the Redis image.
Align everything on a single version to save a few MB of network
bandwidth when bootstrapping the stack.

Late-night minor optimization.
2026-10-02 15:59:04 +02:00
leo f673c07cb8 ✨(backend) add per-recording encoding config to start-recording API
Add new options to query start-start recording API. A resolution
("540p", "720p", "1080p") and a profile ("talking_heads", "text", "mixed")
are resolved to provide a width, height, fps and bitrate which
are passed on to the encoder. Using profiles allows for some flexibility
on quality if necessary without changing front facing user config.

Co-authored-by: sarthakbahal <sarthakbahal.45@gmail.com>
2026-10-02 14:16:01 +02:00
584 changed files with 35329 additions and 8771 deletions
+17 -8
View File
@@ -2,19 +2,28 @@
# Review regularly and remove entries once Debian ships a fix.
# util-linux
CVE-2026-76642
CVE-2026-78408
CVE-2026-78409
CVE-2026-78410
CVE-2026-76642 exp:2026-12-05
CVE-2026-78408 exp:2026-12-05
CVE-2026-78409 exp:2026-12-05
CVE-2026-78410 exp:2026-12-05
# acl
CVE-2026-54369
CVE-2026-54369 exp:2026-12-05
# ncurses
CVE-2025-69720
CVE-2025-69720 exp:2026-12-05
# systemd
CVE-2026-16742
CVE-2026-16742 exp:2026-12-05
# perl-base (fix deferred by Debian)
CVE-2026-9538
CVE-2026-9538 exp:2026-12-05
# libsqlite3-0 (fixed in sid 3.54.1-1; trixie marked no-dsa / minor)
CVE-2026-119373 exp:2026-12-05
CVE-2026-119374 exp:2026-12-05
CVE-2026-119379 exp:2026-12-05
# zlib (fixed in sid 1:1.3.dfsg+really1.3.2-4; trixie still vulnerable)
CVE-2026-76844 exp:2026-12-05
CVE-2026-85091 exp:2026-12-05
+31
View File
@@ -88,6 +88,8 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
with:
persist-credentials: false
- name: Create writable /data
run: |
@@ -159,6 +161,8 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
with:
persist-credentials: false
- name: Install ffmpeg
run: |
@@ -186,6 +190,8 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
with:
persist-credentials: false
- name: Install dependencies
run: cd src/frontend/ && npm ci --ignore-scripts
@@ -196,6 +202,27 @@ jobs:
- name: Check format
run: cd src/frontend/ && npm run check
test-front:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- name: Checkout repository
uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
with:
persist-credentials: false
- name: Install Node.js
uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
with:
node-version: "24.22.1"
- name: Install dependencies
run: cd src/frontend/ && npm ci --ignore-scripts
- name: Run tests
run: cd src/frontend/ && npm test
lint-sdk:
runs-on: ubuntu-latest
permissions:
@@ -206,6 +233,8 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
with:
persist-credentials: false
- name: Install dependencies
run: npm ci --ignore-scripts
@@ -227,6 +256,8 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
with:
persist-credentials: false
- name: Install dependencies
run: npm ci --ignore-scripts
+3
View File
@@ -89,3 +89,6 @@ docker/livekit/rootCA.pem
# NixOS
.devenv
# Zensical build document site
/site/
.pre-commit-config.yaml
+3
View File
@@ -22,6 +22,9 @@
# See http://jorisroovers.github.io/gitlint/user_defined_rules for details
extra-path=gitlint/
# Use "search" semantics for regexes (gitlint's future default)
regex-style-search=True
# [title-max-length]
# line-length=80
+164 -1
View File
@@ -10,8 +10,163 @@ and this project adheres to
### Added
- 📝(doc) create complete documentation website for Meet
- 🌐(i18n) add Portuguese language support
- ✨(frontend) add jittered exponential backoff to LiveKit reconnections
- ✨(frontend) tell participants when a recording is interrupted
### Changed
- ✨(backend) create LiveKit rooms server-side before handing out join tokens
- ⬆️(frontend) upgrade livekit-client to 2.23.0
- ✨(backend) expose LiveKit reconnection settings in the config
- ✨(backend) keep recordings cut short by LiveKit egress
- ⬆️(dev) upgrade LiveKit server to v1.13.11 and egress to v1.15.0
- ⬆️(backend) update python dependencies
- ⬆️(agents) update python dependencies
- ⬆️(summary) update python dependencies
- 🔒️(backend) issue room access tokens via POST rooms/{id}/join/ only
- 🔒️(frontend) send the display name in the join request body
- 🔥(backend) drop is_administrable from unregistered room payloads
- 🍱(frontend) add Portuguese glyphs to Marianne subsetted fonts
- 🚸(frontend) bring new speakers to the top of the carousel
- 🚸(frontend) bring raised hands into view in the carousel
### Fixed
- 📌(summary) pin kombu to keep celery workers compatible with redis 5
- 🐛(frontend) show a page when the connection ends unexpectedly
- 🐛(frontend) show the transcript mic hint when every mic is muted
- 🐛(frontend) show join errors instead of silently waiting in the lobby
- 🐛(frontend) send users who cannot enter directly back to the lobby
- 🔒️(backend) refuse unregistered rooms whose slug is a UUID
- 🔒️(agents) upgrade python to 3.14.10 to fix CVE-2026-109518
- 🔒️(docker) upgrade musl-utils to 1.2.6-r3 to fix CVE-2026-107891
- ♿️(frontend) close the invite dialog with the Escape key #1916
- 🔒️(docker) move frontend to nginx/nginx-unprivileged image
- 🐛(frontend) accept meeting links with query params in join dialog
- 🐛(backend) allow muting when everyone_can_mute is stored as null #1942
- 🐛(frontend) apply the sans font token on every page
- 🐛(frontend) promote the active speaker in the carousel layout
- ♿️(frontend) show the focus ring on connection test detail cards
- ♿️(frontend) use a heading for every connection test card title
- ♿️(frontend) put the ProConnect link label inside the link
## [1.37.0] - 2026-11-01
### Changed
- ⬆️(summary) update ffmpeg to 8.1.3-r0
- ✨(frontend) replace the Crisp chat with the La Suite support form
- 🔒️(frontend) keep rooms out of search engine and AI indexes
- ⬆️(backend) upgrade django-lasuite to v1.0.0
- ⚡️(docker) build frontend assets natively for arm64 images
### Fixed
- 🔒️(summary) protect signed URLs in models, source logs and analytics metadata
- 🔒️(summary) mask secret validation inputs and sanitize upstream and task errors
- 🔒️(summary) scrub sensitive Sentry event and breadcrumb content while retaining
redacted frame locals and application DEBUG diagnostics
## [1.36.3] - 2026-10-23
### Fixed
- 🔒️(backend) upgrade brotli to 1.2.1 to fix CVE-2026-111497
- 🔒️(frontend) upgrade nginx to 1.30.6 to fix CVE-2026-15176
- 🔒️(docker) upgrade brotli-libs to 1.2.1 to fix CVE-2026-111497
- 🔒️(frontend) build the Outlook add-in on Node 22.23.4
- 🔒️(backend) upgrade djangorestframework to 3.18.2 to fix CVE-2026-114136,
CVE-2026-114137 and CVE-2026-114138
## [1.36.2] - 2026-10-21
### Fixed
- 🔒️(frontend) upgrade Node to 22.23.4 and 24.22.1 security releases
## [1.36.1] - 2026-10-21
### Changed
- 🔖(helm) release chart 0.0.28
### Fixed
- 🔒️(docker) distrust compromised eMudhra emSign G3 CA roots
- 🔒️(backend) upgrade pillow to 13.0.0 to fix CVE-2026-112403
## [1.36.0] - 2026-10-20
### Added
- ⚡️(backend) add UPPER(email) index for case-insensitive user lookups
- ✨(backend) add room soft-deletion to the external API
- ✨(all) allow any authenticated user to start a recording
- ✨(backend) authenticate external API calls with Menshen exchanged tokens
- ✨(backend) audit Menshen calls and users created from introspected tokens
### Fixed
- 🔒️(frontend) upgrade libx11 to fix CVE-2026-88806
- 🔒️(backend) throttle the start recording endpoint
- 🐛(backend) put a timeout on every LiveKit API call
- 🔒️(backend) upgrade aiohttp to 3.14.5 to fix CVE-2026-111064
- ♿️(frontend) announce the microphone turning off on shortcut #1816
- 🐛(release) use env bash in prepare-release script for NixOS
## [1.35.0] - 2026-10-13
### Added
- ✨(frontend) let users pick the recording encoding
- ✨(backend) introduce a token exchange endpoint for iframe embeds
- ⚡️(backend) send recording notification emails from a Celery task
- ✨(backend) allow static feature flags without an analytics backend #1809
- ⚡️(backend) add an opt-in psycopg connection pool
### Changed
- ⚡️(backend) hash application secrets with SHA-256
- ⚡️(backend) reduce domain queries on the application token endpoint
- ♻️️️(backend) use a dedicated auth scheme for LiveKit token auth
- ♻️(all) stop relying on cookies for the lobby flow
- ♿️(frontend) show a visible focus outline on menu items #1797
- ⬆️(backend) upgrade pylint to 4.1.3
### Fixed
- 🔒️(backend) prevent editing client id and secret in Django admin
- 🔒️(frontend) upgrade tiff to fix CVE-2026-4775
- 🔒️(backend) bind accepted lobby entries to the current username
- 🔒️(backend) sign lobby participant id
- 🐛(frontend) omit the default speaker id sent to LiveKit
- 🐛(frontend) play the speaker test when no output is picked
- 🐛(frontend) keep the admin panel in place when changing a setting #1804
## [1.34.0] - 2026-10-07
### Added
- ✨(helm) import environment variables from Secrets and ConfigMaps
- 🔒(backend) throttle meeting link generation
- 🔒️(backend) add a daily cap on room creation
- 🔧(summary) add setting to control Sentry traces sampling rate
- ✨(frontend) let signed-out visitors start a meeting
- ✨(backend) expose `allow_unregistered_rooms` in the frontend configuration
- ✅(frontend) add vitest so the frontend can carry unit tests
- ♿️(frontend) make participant pagination readable and keyboard reachable #1775
- ✨(backend) add structured audit logging facility
- ✨(backend) audit external API token and room operations
- 🔒️(backend) audit writes and bulk actions made in the Django admin
- ✨(backend) audit recordings, transcripts and summaries
- ✨(backend) audit transit code issuance and exchange
### Changed
- ✨(frontend) warn users when the connection falls back to TURN
- 🔧(backend) configure the technical documentation url
### Fixed
@@ -19,6 +174,13 @@ and this project adheres to
- 🔒️(agents) fix util-linux CVEs reported by Cyberwatch
- 🔒️(backend) fix HIGH CVEs in Django and urllib3
- 🔒️(agents) upgrade libpcre2-8-0 to fix CVE-2026-103111
- 🔒️(frontend) upgrade pcre2 to fix CVE-2026-103111
- 🐛(summary) disable default S3 checksums for GCS-compatible storage
- 🔒️(summary) redact meeting content from Sentry events
- 🐛(frontend) hide tooltips until they have a computed placement
- 🐛(brevo) use django-lasuite for marketing management
- ♿️(frontend) expose loading state to assistive technology
- 🐛(frontend) honour Keep hand raised when picture-in-picture is open
## [1.33.0] - 2026-09-30
@@ -35,6 +197,7 @@ and this project adheres to
- ♻️(agents) replace the minio client by boto3
- 🔧(compose) replace MinIO by Garage for local development
- 🔧(helm) point media services to Garage by default
- 💥(backend) replace recording encoding options with a profile model
### Fixed
@@ -76,7 +239,7 @@ and this project adheres to
### Fixed
- 🐛(helm) probe liveness on __lbheartbeat__ and readiness on __heartbeat__
- 🐛(helm) probe liveness on `__lbheartbeat__` and readiness on `__heartbeat__`
- 🐛(helm) render periodSeconds and failureThreshold on probes
- 🐛(backend) report the app release to Sentry instead of "NA"
- 🐛(frontend) play the waiting room notification sound on every arrival
+118 -11
View File
@@ -7,6 +7,13 @@ To get started with the project, please refer to the [README.md](https://github.
Please also check out our [dev handbook](https://suitenumerique.gitbook.io/handbook) to learn our best practices.
## Before You Start
- A small fix, a typo or an obvious bug, can go straight to a pull request.
- Before a larger change, or one written with the help of AI, agree on the approach with a maintainer on the [Matrix channel](https://matrix.to/#/#meet-official:matrix.org), as the [README](https://github.com/suitenumerique/meet/blob/main/README.md#contributing) asks.
- [Develop locally](https://documentation-meet.beta.numerique.gouv.fr/contributing/develop/) sets up the code and explains every command. With an AI coding assistant, point it at that page and at [What CI Checks](#what-ci-checks).
## Creating an Issue
When creating an issue, please provide the following details:
@@ -18,50 +25,146 @@ When creating an issue, please provide the following details:
5. **Labels**: Add appropriate labels to categorize the issue (e.g., bug, feature request, documentation).
## Workflow
1. Fork [suitenumerique/meet](https://github.com/suitenumerique/meet) on GitHub, clone your fork, and add the project as a second remote:
```bash
git clone https://github.com/<you>/meet.git && cd meet
git remote add upstream https://github.com/suitenumerique/meet.git
```
2. Create a branch from the project's latest `main`:
```bash
git fetch upstream
git switch -c my-change upstream/main
```
3. Commit in steps, each one change that builds and passes the tests on its own: maintainers may merge commits as they are.
4. Add a line to `CHANGELOG.md`, as [Changelog Update](#changelog-update) describes.
5. Go through the [Checklist](#checklist).
6. Push to your fork and open the pull request against `main`.
7. To bring the branch up to date, rebase it rather than merging `main` into it:
```bash
git fetch upstream
git rebase upstream/main
git push --force-with-lease
```
## Commit Message Format
All commit messages must adhere to the following format:
`<gitmoji>(type) title description`
```
<gitmoji>(<scope>) <title>
* <**gitmoji**>: Use a gitmoji to represent the purpose of the commit. For example, ✨ for adding a new feature or 🔥 for removing something, see the list here: <https://gitmoji.dev/>.
* **(type)**: Describe the type of change. Common types include `backend`, `frontend`, `CI`, `docker` etc...
<description>
```
* <**gitmoji**>: Use a gitmoji to represent the purpose of the commit. For example, ✨ for adding a new feature or 🔥 for removing something. Copy it from the list at <https://gitmoji.dev/>: some, such as 🔒️, end in an invisible character that an emoji picker can leave out, and gitlint then rejects the title.
* **(scope)**: The part of the repository the change touches, such as `backend`, `frontend`, `summary`, `helm`, `ci` or `docs`.
* **title**: A short, descriptive title for the change, starting with a lowercase character.
* **description**: Include additional details about what was changed and why.
To see the scopes in use, most used first:
```bash
git log -300 --format=%s upstream/main | sed -n 's/^[^(]*(\([^)]*\)).*/\1/p' |
sort | uniq -c | sort -rn
```
CI checks every commit with gitlint, using [`.gitlint`](https://github.com/suitenumerique/meet/blob/main/.gitlint) and the rule in [`gitlint/gitlint_emoji.py`](https://github.com/suitenumerique/meet/blob/main/gitlint/gitlint_emoji.py). Run the same check before pushing:
```bash
# From the repository root, with network access:
# the gitmoji rule downloads the gitmoji list
uvx --from gitlint-core gitlint --commits upstream/main..HEAD
```
The [devenv shell](https://documentation-meet.beta.numerique.gouv.fr/contributing/develop/#nix-with-devenv) installs gitlint as a commit-message hook, so it runs on every commit.
### Example Commit Message
```
✨(frontend) add user authentication logic
✨(frontend) add user authentication logic
Implemented login and signup features, and integrated OAuth2 for social login.
```
## Changelog Update
Please add a line to the changelog describing your development. The changelog entry should include a brief summary of the changes, this helps in tracking changes effectively and keeping everyone informed. We usually include the title of the pull request, followed by the pull request ID to finish the log entry. The changelog line should be less than 80 characters in total.
Please add a line to the [changelog](https://github.com/suitenumerique/meet/blob/main/CHANGELOG.md) describing your development, under `## [Unreleased]`, in the `### Added`, `### Changed` or `### Fixed` section. The changelog entry should include a brief summary of the changes, this helps in tracking changes effectively and keeping everyone informed. The line is usually the commit title, sometimes ended with the pull request number.
CI fails the pull request when:
- `CHANGELOG.md` is unchanged, unless a maintainer adds the `noChangeLog` label.
- A line other than a link reference is 80 characters or more. The `wc -L` command in [What CI Checks](#what-ci-checks) checks it: in a UTF-8 terminal it counts most gitmojis as two columns, so it can read more than CI does, and a line under 80 there passes.
### Example Changelog Message
```
## [Unreleased]
## Added
### Added
- ✨(frontend) add AI to the project #321
```
## What CI Checks
These jobs run on each pull request to `main`, most through shared workflows from [suitenumerique/ci](https://github.com/suitenumerique/ci). Each one runs locally:
| Workflow | Run it locally |
|---|---|
| [Project quality](https://github.com/suitenumerique/meet/blob/main/.github/workflows/code-quality.yml), commits | `git diff upstream/main..HEAD -- src/backend src/summary src/agents \| grep -E '^\+.*\bprint\('` must print nothing, then the gitlint command of [Commit Message Format](#commit-message-format) and the `fixup!` check of [Code Review](#code-review) |
| Project quality, spelling | `uvx codespell`, which reads [`.codespellrc`](https://github.com/suitenumerique/meet/blob/main/.codespellrc) |
| Project quality, shell scripts | `shellcheck --external-sources <file>.sh` |
| [Changelog](https://github.com/suitenumerique/meet/blob/main/.github/workflows/changelog.yml) | `grep -Ev '^\[.*\]: https://github.com' CHANGELOG.md \| wc -L` must print less than 80 |
| [CI](https://github.com/suitenumerique/meet/blob/main/.github/workflows/ci.yml), Python lint | `make lint`, then commit what it changed |
| CI, backend tests | `make test-back-parallel` |
| CI, summary tests | `make test-summary` |
| CI, frontend lint and tests | `make frontend-lint`, `make frontend-format`, `make test-frontend` |
| CI, SDK | `cd src/sdk/library && npm ci && npm run lint && npm run check && npm run build` |
| [Docker Hub](https://github.com/suitenumerique/meet/blob/main/.github/workflows/docker-hub.yml) | `npm run build` in `src/frontend` for the type errors; `docker build --build-arg DOCKER_USER=$(id -u):$(id -g) --target backend-production .` for the backend, and `--target production` in `src/summary` or `src/agents` when you touch them. CI also fails an image on a HIGH or CRITICAL Trivy finding |
| [Security analysis](https://github.com/suitenumerique/meet/blob/main/.github/workflows/security.yml) | `uvx zizmor .github/workflows` |
## Pull Requests
It is nice to add information about the purpose of the pull request to help reviewers understand the context and intent of the changes. If you can, add some pictures or a small video to show the changes.
### Don't forget to:
- check your commits
- check the linting: `make lint && make frontend-lint`
- check the tests: `make test`
- add a changelog entry
### Checklist
- [ ] Every job in [What CI Checks](#what-ci-checks) passes locally.
- [ ] The change has tests.
- [ ] A model change comes with its migration, from `make makemigrations`.
- [ ] An External API change is reflected in [`docs/reference/openapi.yaml`](https://github.com/suitenumerique/meet/blob/main/docs/reference/openapi.yaml), and in `resource_server.yaml` beside it when the user's OIDC token routes change.
- [ ] Every new or changed string is translated in the five frontend languages, and in the backend catalogs when it is a backend string, see [Translations](https://documentation-meet.beta.numerique.gouv.fr/contributing/develop/#translations).
- [ ] An interface change works with the keyboard alone, every control has a name a screen reader reads, and the description shows it with screenshots.
- [ ] A new or changed setting is documented in [Environment variables](https://documentation-meet.beta.numerique.gouv.fr/reference/env-variables/), and a user-visible change on the page that describes the feature.
- [ ] A change that asks operators to do something when they upgrade is described in [`UPGRADE.md`](https://github.com/suitenumerique/meet/blob/main/UPGRADE.md).
- [ ] No secret, password or key is committed.
Once all the required tests have passed, you can request a review from the project maintainers.
## Code Review
A maintainer reviews the pull request. Keep it to one change: a fix and a refactor go in two pull requests, so neither waits on the other.
CI rejects `fixup!` and `squash!` commits, so a review fix goes into the commit it belongs to, not a new one on top:
```bash
# Record the fix against the commit it amends
git commit --fixup=<sha of that commit>
# Fold every fixup into its target: save the list the editor opens.
# Keep -i: Git before 2.44 ignores --autosquash without it.
git rebase -i --autosquash upstream/main
# Check that no fixup! or squash! title remains: this prints nothing
git log --format=%s upstream/main..HEAD | grep -E '^(fixup|squash)!'
# Replace the branch on your fork
git push --force-with-lease
```
## Code Style
Please maintain consistency in code style. Run any linting tools available to make sure the code is clean and follows the project's conventions.
@@ -70,6 +173,10 @@ Please maintain consistency in code style. Run any linting tools available to ma
Make sure that all new features or fixes have corresponding tests. Run the test suite before pushing your changes to ensure that nothing is broken.
## Security
Never report, discuss or fix a vulnerability in a public issue or pull request first: report it privately, as [SECURITY.md](https://github.com/suitenumerique/meet/blob/main/SECURITY.md) describes.
## Asking for Help
If you need any help while contributing, feel free to open a discussion or ask for guidance in the issue tracker. We are more than happy to assist!
+13 -8
View File
@@ -1,14 +1,17 @@
# Django Meet
# ---- base image to inherit from ----
FROM python:3.13.15-alpine3.24 AS base
FROM python:3.13.16-alpine3.24 AS base
# Upgrade pip to its latest release to speed up dependencies installation
RUN python -m pip install --upgrade pip
# Upgrade system packages to install security updates
RUN apk update && \
apk upgrade
apk upgrade && \
apk add --no-cache --upgrade 'ca-certificates>=20261020-r0' \
'musl-utils>=1.2.6-r3' && \
update-ca-certificates
# ---- Back-end builder image ----
FROM base AS back-builder
@@ -23,7 +26,7 @@ ENV UV_LINK_MODE=copy
ENV UV_PYTHON_DOWNLOADS=0
# install uv
COPY --from=ghcr.io/astral-sh/uv:0.10.9 /uv /uvx /bin/
COPY --from=ghcr.io/astral-sh/uv:0.13.4 /uv /uvx /bin/
WORKDIR /app
@@ -37,14 +40,15 @@ RUN --mount=type=cache,target=/root/.cache/uv \
uv sync --locked --no-dev
# ---- mails ----
FROM node:22 AS mail-builder
FROM node:22.23.4-alpine AS mail-builder
RUN apk upgrade --no-cache ca-certificates
COPY ./src/mail /mail/app
WORKDIR /mail/app
RUN yarn install --frozen-lockfile && \
yarn build
RUN npm ci --ignore-scripts && npm run build
# ---- static link collector ----
@@ -84,7 +88,8 @@ RUN apk --no-cache add \
libffi-dev \
pango \
libmagic \
shared-mime-info
shared-mime-info \
'brotli-libs>=1.2.1-r0'
# Copy entrypoint
@@ -121,7 +126,7 @@ USER root:root
RUN apk add postgresql-client
# Install development dependencies
RUN --mount=from=ghcr.io/astral-sh/uv:0.10.9,source=/uv,target=/bin/uv \
RUN --mount=from=ghcr.io/astral-sh/uv:0.13.4,source=/uv,target=/bin/uv \
uv sync --all-extras --locked
# Restore the un-privileged user running the application
+7 -3
View File
@@ -169,7 +169,7 @@ run-summary: ## start only the summary application and all needed services
@$(COMPOSE) up --force-recreate -d celery-summary-summarize
.PHONY: run-summary
run-agents: ## start the multi-user-transcriber agent
run-agents: ## start the LiveKit agents (opt-in, see docs/contributing/develop.md)
@$(MAKE) run-agent-multi-user-transcriber
@$(MAKE) run-agent-metadata-collector
.PHONY: run-agents
@@ -186,7 +186,6 @@ run:
run: ## start the wsgi (production) and development server
@$(MAKE) run-backend
@$(MAKE) run-summary
@$(MAKE) run-agents
@$(COMPOSE) up --force-recreate -d frontend
.PHONY: run
@@ -260,7 +259,8 @@ lint-pylint: ## lint back-end python sources with pylint only on changed files f
test: ## run project tests; pass extra pytest args via ARGS, e.g. `make test ARGS="-vv"`
@args="$(ARGS) $(filter-out $@,$(MAKECMDGOALS))" && \
$(MAKE) test-back-parallel ARGS="$${args}" && \
$(MAKE) test-summary ARGS="$${args}"
$(MAKE) test-summary ARGS="$${args}" && \
$(MAKE) test-frontend
.PHONY: test
test-back: ## run back-end tests (pass extra pytest args via ARGS)
@@ -278,6 +278,10 @@ test-summary: ## run summary tests (pass extra pytest args via ARGS)
bin/pytest-summary $${args}
.PHONY: test-summary
test-frontend: ## run the frontend unit tests
cd $(PATH_FRONT) && npm test
.PHONY: test-frontend
makemigrations: ## run django makemigrations for the Meet project.
@echo "$(BOLD)Running makemigrations$(RESET)"
@$(COMPOSE) up -d postgresql
+18 -27
View File
@@ -11,7 +11,7 @@
<img alt="GitHub commit activity" src="https://img.shields.io/github/commit-activity/m/suitenumerique/meet"/>
<img alt="GitHub closed issues" src="https://img.shields.io/github/issues-closed/suitenumerique/meet"/>
<a href="https://github.com/suitenumerique/meet/blob/main/LICENSE">
<img alt="GitHub closed issues" src="https://img.shields.io/github/license/suitenumerique/meet"/>
<img alt="GitHub license" src="https://img.shields.io/github/license/suitenumerique/meet"/>
</a>
<a href="https://digitalpublicgoods.net/r/la-suite-meet-simple-video-conferencing">
<img src="https://img.shields.io/badge/Verified-DPG-3333AB?logo=data:image/svg%2bxml;base64,PHN2ZyB3aWR0aD0iMzEiIGhlaWdodD0iMzMiIHZpZXdCb3g9IjAgMCAzMSAzMyIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj4KPHBhdGggZD0iTTE0LjIwMDggMjEuMzY3OEwxMC4xNzM2IDE4LjAxMjRMMTEuNTIxOSAxNi40MDAzTDEzLjk5MjggMTguNDU5TDE5LjYyNjkgMTIuMjExMUwyMS4xOTA5IDEzLjYxNkwxNC4yMDA4IDIxLjM2NzhaTTI0LjYyNDEgOS4zNTEyN0wyNC44MDcxIDMuMDcyOTdMMTguODgxIDUuMTg2NjJMMTUuMzMxNCAtMi4zMzA4MmUtMDVMMTEuNzgyMSA1LjE4NjYyTDUuODU2MDEgMy4wNzI5N0w2LjAzOTA2IDkuMzUxMjdMMCAxMS4xMTc3TDMuODQ1MjEgMTYuMDg5NUwwIDIxLjA2MTJMNi4wMzkwNiAyMi44Mjc3TDUuODU2MDEgMjkuMTA2TDExLjc4MjEgMjYuOTkyM0wxNS4zMzE0IDMyLjE3OUwxOC44ODEgMjYuOTkyM0wyNC44MDcxIDI5LjEwNkwyNC42MjQxIDIyLjgyNzdMMzAuNjYzMSAyMS4wNjEyTDI2LjgxNzYgMTYuMDg5NUwzMC42NjMxIDExLjExNzdMMjQuNjI0MSA5LjM1MTI3WiIgZmlsbD0id2hpdGUiLz4KPC9zdmc+Cg==" alt="DPG Badge"/>
@@ -24,13 +24,13 @@
<p align="center">
<a href="https://visio.numerique.gouv.fr/">
<img src="https://github.com/user-attachments/assets/09c1faa1-de88-4848-af3a-6fbe793999bf" alt="La Suite Meet Demonstration">
<img src="https://github.com/user-attachments/assets/09c1faa1-de88-4848-af3a-6fbe793999bf" alt="LaSuite Meet Demonstration">
</a>
</p>
## La Suite Meet: Simple Video Conferencing
## LaSuite Meet: Simple Video Conferencing
Powered by [LiveKit](https://livekit.io/), La Suite Meet offers Zoom-level performance with high-quality video and audio. No installation required—simply join calls directly from your browser. Check out LiveKit's impressive optimizations in their [blog post](https://blog.livekit.io/livekit-one-dot-zero/).
Powered by [LiveKit](https://livekit.io/), LaSuite Meet offers Zoom-level performance with high-quality video and audio. No installation required—simply join calls directly from your browser. Check out LiveKit's impressive optimizations in their [blog post](https://blog.livekit.io/livekit-one-dot-zero/).
> [!TIP]
> New here? Start by introducing yourself in our Matrix channel:
@@ -49,21 +49,23 @@ Powered by [LiveKit](https://livekit.io/), La Suite Meet offers Zoom-level perfo
- Telephony integration
- Secure participation with robust authentication and access control
- Customizable frontend style
- LiveKit Advances features including :
- speaker detection
- LiveKit advanced features including:
- speaker detection
- simulcast
- end-to-end optimizations
- selective subscription
- SVC codecs (VP9, AV1)
La Suite Meet is fully self-hostable and released under the MIT License, ensuring complete control and flexibility. It's simple to [get started](https://visio.numerique.gouv.fr/) or [request a demo](mailto:visio@numerique.gouv.fr).
LaSuite Meet is fully self-hostable and released under the MIT License, ensuring complete control and flexibility. It's simple to [get started](https://visio.numerique.gouv.fr/) or [request a demo](mailto:visio@numerique.gouv.fr).
We’re continuously adding new features to enhance your experience, with the latest updates coming soon!
⭐ **Find LaSuite Meet useful?** Click the Star button at the top right of this page. It helps other people and public organizations discover the project.
### 🚀 Major roll out to all French public servants
On the 29th of January 2026, Prime Minister Sébastien Lecornu, announced the full deployment of Visio—the French government’s dedicated Meet platform—to all public servants. ([Source in English](https://www.nytimes.com/2026/01/29/world/europe/france-zoom-alternative-visio.html))
On the 29th of January 2026, Prime Minister Sébastien Lecornu announced the full deployment of Visio—the French government’s dedicated Meet platform—to all public servants. ([Source in English](https://www.nytimes.com/2026/01/29/world/europe/france-zoom-alternative-visio.html))
## Table of Contents
@@ -79,30 +81,19 @@ On the 29th of January 2026, Prime Minister Sébastien Lecornu, announced the fu
## Docs
We're currently working on both technical and user documentation for La Suite Meet. In the meantime, many of the essential aspects are already well covered by the [LiveKit documentation](https://docs.livekit.io/home/) and their [self-hosting guide](https://docs.livekit.io/home/self-hosting/deployment/). Stay tuned for more updates!
The documentation, for users, administrators and integrators, is at [documentation-meet.beta.numerique.gouv.fr](https://documentation-meet.beta.numerique.gouv.fr/).
## Self-host
### La Suite Meet is easy to install on your own servers
### LaSuite Meet is easy to install on your own servers
We use Kubernetes for our [production instance](https://visio.numerique.gouv.fr/) but also support Docker Compose. The community contributed a couple other methods (Nix, YunoHost etc.) check out the [docs](/docs/installation/README.md) to get detailed instructions and examples.
We use Kubernetes for our [production instance](https://visio.numerique.gouv.fr/) but also support Docker Compose. The community contributed a couple of other methods (Nix, YunoHost, etc.); check out the [docs](/docs/self-hosting/index.md) for detailed instructions and examples.
**Questions?** Open an issue on [GitHub](https://github.com/suitenumerique/meet/issues/new?assignees=&labels=bug&template=Bug_report.md) or join our [Matrix community](https://matrix.to/#/#meet-official:matrix.org).
> [!NOTE]
> Some advanced features (ex: recording, transcription) lack detailed documentation. We're working hard to provide comprehensive guides soon.
#### Known instances
We hope to see many more, here is an incomplete list of public La Suite Meet instances. Feel free to make a PR to add ones that are not listed below🙏
| Url | Org | Access |
|---------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
| [visio.numerique.gouv.fr](https://visio.numerique.gouv.fr/) | DINUM | French public agents working for the central administration and the extended public sphere. ProConnect is required to login in or sign up |
| [visio.suite.anct.gouv.fr](https://visio.suite.anct.gouv.fr/) | ANCT | French public agents working for the territorial administration and the extended public sphere. ProConnect is required to login in or sign up |
| [visio.lasuite.coop](https://visio.lasuite.coop/) | lasuite.coop | Free and open demo to all. Content and accounts are reset after one month |
| [mosacloud.cloud](https://mosa.cloud/) | mosa.cloud | Demo instance of mosa.cloud, a dutch company providing services around La Suite apps. |
| [Clever Cloud](https://www.clever.cloud/product/visio/) | clever cloud | Openvisio is a sovereign video conferencing solution based on LaSuite Meet offered by [Clever Cloud](https://www.clever.cloud/). |
| [Email.eu](https://email.eu/) | Email.eu | Sovereign business workspace. |
The public instances are listed in the [documentation](https://documentation-meet.beta.numerique.gouv.fr/#known-public-instances). Feel free to make a PR adding yours to [`docs/index.md`](docs/index.md).
# Contributing
@@ -135,7 +126,7 @@ Open source is much more than code. Writing documentation, improving onboarding,
When you’re ready, here are a few ways to get involved:
* 👋 **Say hello** and share your ideas with the community and maintainers on our [Matrix channel](https://matrix.to/#/#meet-official:matrix.org)
* 🛠️ **Open a PR** by following our guide to [develop La Suite Meet locally](https://github.com/suitenumerique/meet/blob/main/docs/developping_locally.md)
* 🛠️ **Open a PR** by following our guide to [develop LaSuite Meet locally](https://github.com/suitenumerique/meet/blob/main/docs/contributing/develop.md)
* 💡 **Suggest an idea** by opening a [feature request](https://github.com/suitenumerique/meet/issues/new?assignees=&labels=enhancement&template=Feature_request.md)
* 🐛 **Report a bug** by opening a [bug report](https://github.com/suitenumerique/meet/issues/new?assignees=&labels=bug&template=Bug_report.md)
@@ -149,9 +140,9 @@ Whether you’re actively contributing or just curious about the project, you’
## Philosophy
We’re relentlessly focused on building the best open-source video conferencing product—La Suite Meet. Growth comes from creating something people truly need, not just from chasing metrics.
We’re relentlessly focused on building the best open-source video conferencing product—LaSuite Meet. Growth comes from creating something people truly need, not just from chasing metrics.
Our users come first. We’re committed to making La Suite Meet as accessible and easy to use as proprietary solutions, ensuring it meets the highest standards.
Our users come first. We’re committed to making LaSuite Meet as accessible and easy to use as proprietary solutions, ensuring it meets the highest standards.
Most of the heavy engineering is handled by the incredible LiveKit team, allowing us to focus on delivering a top-tier product. We follow extreme programming practices, favoring pair programming and quick, iterative releases. Challenge our tech and architecture—simplicity is always our top priority.
@@ -165,7 +156,7 @@ To learn more, don't hesitate to [reach out](mailto:visio@numerique.gouv.fr).
### Help us!
Come help us make La Suite Meet even better. We're growing fast and [would love some help](mailto:visio@numerique.gouv.fr).
Come help us make LaSuite Meet even better. We're growing fast and [would love some help](mailto:visio@numerique.gouv.fr).
## Contributors 🧞
+254 -2
View File
@@ -16,9 +16,261 @@ the following command inside your docker container:
## [Unreleased]
### Compose env files: `KEYCLOAK_HOST` renamed, internal hosts removed
`env.d/production.dist/hosts` and the OIDC endpoints of
`env.d/production.dist/common` now read `IDP_HOST`. If you refresh `common`
from the new templates, rename `KEYCLOAK_HOST` to `IDP_HOST` in your `.env`
too, or the OIDC endpoints get an empty host and login fails.
`hosts` also no longer carries `BACKEND_INTERNAL_HOST`,
`FRONTEND_INTERNAL_HOST` and `LIVEKIT_INTERNAL_HOST`. A deployment that still
mounts `docker/files/production/default.conf.template` needs them in its
`.env`, or the frontend nginx fails to start. The compose examples now use
`docs/examples/meet/nginx-routing.conf` in its place.
### Room access tokens moved to POST /join/
LiveKit access tokens are no longer returned when reading a room. They are henceforth issued by a dedicated `POST
/api/v1.0/rooms/{id}/join/` endpoint, which receives the display name in its JSON body. Display names therefore no
longer appear in URLs and token retrieval by logged-in users is now protected against CSRF.
- `GET /api/v1.0/rooms/{id}/` no longer returns the `livekit` block, and neither do the list, create and update
responses
- The `username` field of `POST /api/v1.0/rooms/{id}/request-entry/` is now limited to 255 characters
- When the caller may enter the room directly, the response contains the room data plus a `livekit` block
- When the caller must go through the lobby, the response has no `livekit` block
- Session-authenticated callers must send the CSRF token (`X-CSRFToken` header and `csrftoken` cookie)
- Every join returning a `livekit` block mints a new token, valid for 6 hours, and anonymous callers get a new
participant identity each time.
- Joining again returns no `livekit` block to callers admitted through the lobby.
- Unregistered rooms are always entered directly: joining one always returns a `livekit` block.
- Unregistered rooms are no longer described with an `is_administrable` field,
### Unregistered rooms can no longer be named after a UUID
When `ALLOW_UNREGISTERED_ROOMS` is enabled, reading or joining a room whose identifier normalizes to an empty slug or to
a UUID now returns a 404 instead of describing or letting callers join the unregistered room.
This closes a lobby bypass since a registered LiveKit room is named after its room id. An identifier crafted to not
parse as a UUID, yet to normalize to an existing room's id, matched no registered room and was treated as an
unregistered one. The token minted for that unregistered room was valid for the registered room: anyone could join a
trusted or restricted room without being admitted through the lobby.
## v1.37.0
### Crisp support chat replaced by the LaSuite support form
The Crisp chat is gone, the support button, now open the LaSuite support form. They are hidden unless these `FRONTEND_SUPPORT` keys are all set.
The former help links for recording/transcription are now redirecting to the adhoc page in the official documentation
### Pages hidden from search engines
Every page except `/` now carries a `noindex` tag and, with the provided nginx configurations, an `X-Robots-Tag` header to stay out of search indexes.
A new `robots.txt` also blocks the main AI crawlers. If you maintain your own nginx configuration, copy the `location = /` and `location = /home.html` blocks from `src/frontend/default.conf`, and the `X-Robots-Tag` header from its `location /`.
### LiveKit server v1.13.11 and egress v1.15.0
The development stack now runs LiveKit server v1.13.11 and LiveKit Egress v1.15.0. When upgrading your own deployment:
- Deploy this release of Meet first, then upgrade egress, then the server. Older Meet releases discard the partial recordings described below.
- Transcripts no longer go through Chrome. Since egress v1.13, audio-only recordings always use the egress SDK pipeline.
- A transcript now waits for actual audio: it stays "starting", and participants are asked to turn on their microphone, while every microphone is muted.
- Recordings cut short are now kept. Since egress v1.14, a transcript that lost the room, or any recording drained because its egress host ran out of CPU, still uploads what it recorded, even though egress may report it as failed. Meet saves and processes it as usual, and tells participants the recording was interrupted. A screen recording that loses the room is still reported as complete, and saved without a warning.
- Telephony: since server v1.13.8, a call that matches no dispatch rule, for example while no room is active, is rejected with a SIP 404 instead of being silently dropped.
## [v1.35.0]
### Purging deleted rooms
Deleting a room now only soft deletes it: it is hidden but keeps its slug and PIN code. The `purge_inactive_rooms` command also permanently deletes soft-deleted rooms. See [the room purge documentation](docs/self-hosting/configuration/room-purge.md).
- Inactive soft-deleted rooms are purged along with the other inactive rooms: if `ROOM_INACTIVITY_DELETION_DAYS` is already set, nothing else is needed.
- The new `ROOM_DELETED_RETENTION_DAYS` setting purges soft-deleted rooms that many days after their deletion, whether they are inactive or not. It is unset by default.
- As for inactive rooms, a deleted room holding a saved recording its users may still access is kept until that recording expires.
### Recording permission
We've introduced the ability for any authenticated participant to start a recording or transcription, but this behavior remains configurable.
You can keep recording and transcription restricted to room admins and owners by setting `RECORDING_AUTHENTICATED_PARTICIPANTS_ENABLED` to `false`.
## [v1.34.0]
### Marketing / Brevo integration now uses `django-lasuite`
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
LaSuite products. Existing lists are now preserved and merged.
**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.
**Configuration changes.** The following environment variables / settings are
**removed** and no longer read:
- `MARKETING_SERVICE_CLASS`
- `BREVO_API_KEY`
- `BREVO_API_CONTACT_LIST_IDS`
- `BREVO_API_CONTACT_ATTRIBUTES` (previous default: `{"VISIO_USER": True}`)
- `BREVO_API_TIMEOUT`
They are replaced by a single `LASUITE_MARKETING` setting, configured through:
| Variable | Default | Description |
| ------------------------------ | ------------------------------------------------ | -------------------------------------------- |
| `LASUITE_MARKETING_BACKEND` | `lasuite.marketing.backends.dummy.DummyBackend` | Backend class path |
| `LASUITE_MARKETING_PARAMETERS` | `{}` | Keyword arguments passed to the backend |
⚠️ The default backend is now a **dummy** (no-op). If you previously used
Brevo, you must explicitly configure it, otherwise signups are silently dropped:
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}}
Migration mapping:
- `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)
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).
### Recording encoding settings replaced by a resolution/profile model
The `RECORDING_ENCODING_*` settings introduced in v1.16.0 exposed raw encoder
values (width, height, framerate, bitrate). They are replaced by two named and configurable sets of
dimensions, a **resolution** (default: `540p`, `720p`, `1080p`) and a **profile**
(default: `talking_heads`, `text`, `mixed`, `full`), which are resolved to the width, height,
fps and video bitrate.
**The following environment variables are no longer read. If they are still set in
your deployment they are silently ignored, and your recordings will be encoded with
the new defaults instead of your tuned values.**
| Removed variable | Replaced by |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `RECORDING_ENCODING_ENABLED` | Nothing. A default encoding is now always built (see below). **Not** `RECORDING_CUSTOM_ENCODING_ENABLED`, which gates a different feature. |
| `RECORDING_ENCODING_WIDTH` | The `width` of the entry selected by `RECORDING_ENCODING_DEFAULT_RESOLUTION` in `RECORDING_ENCODING_AVAILABLE_RESOLUTIONS`. |
| `RECORDING_ENCODING_HEIGHT` | The `height` of that same entry. |
| `RECORDING_ENCODING_FRAMERATE` | The `fps` of the profile selected by `RECORDING_ENCODING_DEFAULT_PROFILE` in `RECORDING_ENCODING_AVAILABLE_PROFILES`. |
| `RECORDING_ENCODING_VIDEO_BITRATE_KBPS` | That profile's `kbps`. |
`RECORDING_ENCODING_AUDIO_BITRATE_KBPS` and `RECORDING_ENCODING_KEY_FRAME_INTERVAL_S`
keep their names and meaning. The keyframe interval now defaults to `0` (unset,
encoder's choice) instead of `4.0`.
#### If you never set `RECORDING_ENCODING_ENABLED=True`
The shipped defaults (`RECORDING_ENCODING_DEFAULT_PROFILE=full`,
`RECORDING_ENCODING_DEFAULT_RESOLUTION=720p`) match LiveKit's built-in
`H264_720P_30` preset: 1280×720, 30 fps, 3000 kbps H.264 MAIN, 128 kbps AAC.
Video output is therefore unchanged.
Audio and keyframing may not be. These values are now sent explicitly as advanced
`EncodingOptions` rather than relying on LiveKit's preset, so
`RECORDING_ENCODING_AUDIO_BITRATE_KBPS` and `RECORDING_ENCODING_KEY_FRAME_INTERVAL_S`
now apply to every recording. They previously applied only when
`RECORDING_ENCODING_ENABLED` was `True`. **If you set either of them while the
feature was disabled, they had no effect and now do**; check them before upgrading.
If you never set them, no action is required: 128 kbps AAC is what the preset used,
and the keyframe interval now defaults to `0`, which leaves the field unset so the
encoder keeps picking it as before. Set `RECORDING_ENCODING_KEY_FRAME_INTERVAL_S=4.0`
if you want fixed 4-second keyframes (the value the setting defaulted to while it
was gated behind `RECORDING_ENCODING_ENABLED`).
To keep letting LiveKit pick the encoding instead, set either default to an empty
value:
```
RECORDING_ENCODING_DEFAULT_RESOLUTION=
RECORDING_ENCODING_DEFAULT_PROFILE=
```
#### If you had tuned `RECORDING_ENCODING_*` values
Translate your old values into a default resolution and a default profile. Declare your own resolution and/or profile. Both maps are read from the
environment as a single-line Python/JSON dict literal (parsed with
`ast.literal_eval`, so use double-quoted keys and no trailing commas, and do not
add outer quotes in `.env`-style files):
```bash
RECORDING_ENCODING_AVAILABLE_RESOLUTIONS={"540p": {"width": 960, "height": 540}, "720p": {"width": 1280, "height": 720}, "1080p": {"width": 1920, "height": 1080}}
RECORDING_ENCODING_AVAILABLE_PROFILES={"my_old_profile": {"fps": 15, "kbps": {"540p": 350, "720p": 600, "1080p": 1100}}}
RECORDING_ENCODING_DEFAULT_RESOLUTION=720p
RECORDING_ENCODING_DEFAULT_PROFILE=my_old_profile
```
Both maps are validated at startup and a malformed one raises a `ValueError`:
- every entry of `RECORDING_ENCODING_AVAILABLE_RESOLUTIONS` must declare `width` and
`height`, and every entry of `RECORDING_ENCODING_AVAILABLE_PROFILES` an `fps` and a
`kbps` map;
- every profile must define a `kbps` entry for **exactly** the keys of
`RECORDING_ENCODING_AVAILABLE_RESOLUTIONS`; overriding one of the two maps usually
means overriding both;
- `RECORDING_ENCODING_DEFAULT_RESOLUTION` and `RECORDING_ENCODING_DEFAULT_PROFILE`,
when non-empty, must be keys of their respective map.
#### Breaking: custom worker services must accept `encoding_options`
Only concerns deployments pointing `RECORDING_WORKER_CLASSES` at their own worker
class. The shipped `VideoCompositeEgressService` and `AudioCompositeEgressService`
are already updated.
The `WorkerService` protocol's `start()` takes a third argument, and the mediator
now always passes it as a keyword when the recording carries no per-recording encoding:
```python
# before
def start(self, room_id: str, recording_id: str) -> str: ...
# now
def start(
self,
room_id: str,
recording_id: str,
encoding_options: Optional[Dict[str, Any]] = None,
) -> str: ...
```
#### Optional: per-recording encoding
`RECORDING_CUSTOM_ENCODING_ENABLED` (default `False`) toggles whether the
start-recording API accepts an `encoding` object
(`{"resolution": "720p", "profile": "talking_heads"}`, `profile` optional. It
falls back to `RECORDING_ENCODING_DEFAULT_PROFILE`) that overrides the default for
a single recording. It does not enable or disable the
default encoding, which is built from the two `RECORDING_ENCODING_DEFAULT_*`
settings either way. Leaving it at `False` preserves the previous behavior, where
every recording uses the server-side encoding: requests carrying
`options.encoding` are rejected with a `400` before the recording is created, so
nothing is persisted and no egress is started.
Before enabling it:
- clients can only pick keys you declared; there is no way to send a raw width or bitrate
- as of this implementation, the frontend never sends `encoding`
- `encoding` is accepted but ignored for `transcript` recordings, whose audio-only
egress has no video encoding to configure.
See [docs/self-hosting/configuration/recording.md](docs/self-hosting/configuration/recording.md#configuring-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).
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/self-hosting/configuration/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.
@@ -44,7 +296,7 @@ To migrate a local environment:
### 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`, 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.
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
+9 -8
View File
@@ -104,15 +104,16 @@ k8s_yaml(secret_yaml_generic(
k8s_yaml(local('cd ../src/helm && helmfile -n meet -e ${DEV_ENV:-dev-keycloak} template .'))
k8s_resource('garage-cors', resource_deps=['garage'])
k8s_resource('meet-backend', resource_deps=['postgresql', 'garage-cors', 'redis', 'livekit-livekit-server'])
k8s_resource('meet-celery-backend', resource_deps=['redis'])
k8s_resource('meet-celery-summarize', resource_deps=['redis'])
k8s_resource('meet-celery-summary-backend', resource_deps=['redis'])
k8s_resource('meet-celery-transcribe-default', resource_deps=['redis'])
k8s_resource('livekit-livekit-server', resource_deps=['redis'])
k8s_resource('dev-backend-garage-cors', resource_deps=['dev-backend-garage'])
k8s_resource('dev-backend-keycloak', resource_deps=['dev-backend-keycloak-pg'])
k8s_resource('meet-backend', resource_deps=['dev-backend-postgres', 'dev-backend-garage-cors', 'dev-backend-redis', 'dev-backend-keycloak', 'livekit-livekit-server'])
k8s_resource('meet-celery-backend', resource_deps=['dev-backend-redis'])
k8s_resource('meet-celery-summarize', resource_deps=['dev-backend-redis'])
k8s_resource('meet-celery-summary-backend', resource_deps=['dev-backend-redis'])
k8s_resource('meet-celery-transcribe-default', resource_deps=['dev-backend-redis'])
k8s_resource('livekit-livekit-server', resource_deps=['dev-backend-redis'])
k8s_resource('livekit-livekit-server-test-connection', resource_deps=['livekit-livekit-server'])
k8s_resource('keycloak', resource_deps=['kc-postgresql'])
k8s_resource('livekit-egress', resource_deps=['livekit-livekit-server'])
# Trigger once on launch
k8s_resource(
'meet-backend-createsuperuser',
+45 -48
View File
@@ -1,6 +1,6 @@
#!/bin/bash
#!/usr/bin/env bash
set -e # Exit on error
set -e # Exit on error
# Colors for output
RED='\033[0;31m'
@@ -10,60 +10,59 @@ NC='\033[0m' # No Color
# Function to print colored output
print_info() {
echo -e "${GREEN}[INFO]${NC} $1"
echo -e "${GREEN}[INFO]${NC} $1"
}
print_error() {
echo -e "${RED}[ERROR]${NC} $1"
echo -e "${RED}[ERROR]${NC} $1"
}
print_warning() {
echo -e "${YELLOW}[WARNING]${NC} $1"
echo -e "${YELLOW}[WARNING]${NC} $1"
}
# Function to update npm package version
update_npm_version() {
local component=$1
print_info "Updating $component version..."
cd "src/$component"
npm version "$VERSION" --no-git-tag-version
cd -
local component=$1
print_info "Updating $component version..."
cd "src/$component"
npm version "$VERSION" --no-git-tag-version
cd -
}
# Function to update Python project version in pyproject.toml
update_python_version() {
local component=$1
print_info "Updating $component version..."
cd "src/$component"
local component=$1
print_info "Updating $component version..."
cd "src/$component"
if [ ! -f "pyproject.toml" ]; then
print_error "pyproject.toml not found in src/$component!"
exit 1
fi
if [ ! -f "pyproject.toml" ]; then
print_error "pyproject.toml not found in src/$component!"
exit 1
fi
if grep -q '^version = "' pyproject.toml; then
sed -i.bak "s/^version = \".*\"/version = \"$VERSION\"/" pyproject.toml
rm pyproject.toml.bak
print_info "Updated pyproject.toml version to $VERSION"
else
print_error "Could not find version line in pyproject.toml"
exit 1
fi
if grep -q '^version = "' pyproject.toml; then
sed -i.bak "s/^version = \".*\"/version = \"$VERSION\"/" pyproject.toml
rm pyproject.toml.bak
print_info "Updated pyproject.toml version to $VERSION"
else
print_error "Could not find version line in pyproject.toml"
exit 1
fi
cd -
cd -
}
# Check if we're in a git repository
if ! git rev-parse --git-dir > /dev/null 2>&1; then
print_error "Not a git repository. Please run this script from the root of your project."
exit 1
if ! git rev-parse --git-dir >/dev/null 2>&1; then
print_error "Not a git repository. Please run this script from the root of your project."
exit 1
fi
# Check if working directory is clean
if ! git diff-index --quiet HEAD --; then
print_error "Working directory is not clean. Please commit or stash your changes first."
exit 1
print_error "Working directory is not clean. Please commit or stash your changes first."
exit 1
fi
# Ask user for release version number
@@ -72,8 +71,8 @@ read -r -p "Enter release version number (e.g., 1.2.3): " VERSION
# Validate version format (basic semver check)
if ! [[ $VERSION =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
print_error "Invalid version format. Please use semantic versioning (e.g., 1.2.3)"
exit 1
print_error "Invalid version format. Please use semantic versioning (e.g., 1.2.3)"
exit 1
fi
print_info "Release version: $VERSION"
@@ -81,8 +80,8 @@ print_info "Release version: $VERSION"
# Check if branch already exists
BRANCH_NAME="release/$VERSION"
if git show-ref --verify --quiet "refs/heads/$BRANCH_NAME"; then
print_error "Branch $BRANCH_NAME already exists!"
exit 1
print_error "Branch $BRANCH_NAME already exists!"
exit 1
fi
# Create and checkout new branch
@@ -129,8 +128,8 @@ cd -
print_info "Updating CHANGELOG..."
if [ ! -f "CHANGELOG.md" ]; then
print_error "CHANGELOG.md not found in project root!"
exit 1
print_error "CHANGELOG.md not found in project root!"
exit 1
fi
# Get current date in YYYY-MM-DD format
@@ -138,23 +137,21 @@ CURRENT_DATE=$(date +%Y-%m-%d)
# Replace [Unreleased] with [version number] - YYYY-MM-DD
if grep -q '\[Unreleased\]' CHANGELOG.md; then
sed -i.bak "s/\[Unreleased\]/[$VERSION] - $CURRENT_DATE/" CHANGELOG.md
sed -i.bak "s/\[Unreleased\]/[$VERSION] - $CURRENT_DATE/" CHANGELOG.md
# Add new [Unreleased] section after the header
# This adds it after the line containing "Semantic Versioning"
sed -i.bak "/Semantic Versioning/a\\
# Add new [Unreleased] section after the header
# This adds it after the line containing "Semantic Versioning"
sed -i.bak "/Semantic Versioning/a\\
\\
## [Unreleased]
" CHANGELOG.md
rm CHANGELOG.md.bak
print_info "Updated CHANGELOG.md"
rm CHANGELOG.md.bak
print_info "Updated CHANGELOG.md"
else
print_warning "Could not find [Unreleased] section in CHANGELOG.md"
print_warning "Could not find [Unreleased] section in CHANGELOG.md"
fi
# Summary
echo ""
print_info "Release preparation complete!"
@@ -178,4 +175,4 @@ print_warning "Next steps:"
echo " 1. Review the changes: git status"
echo " 2. Commit the changes: git add . && git commit -m 'Release $VERSION'"
echo " 3. Push the branch: git push origin $BRANCH_NAME"
echo ""
echo ""
+21 -23
View File
@@ -5,15 +5,17 @@ services:
env_file:
- env.d/development/postgresql
ports:
- "15432:5432"
- "127.0.0.1:15432:5432"
redis:
image: redis:5
ports:
- "127.0.0.1:6379:6379"
mailcatcher:
image: sj26/mailcatcher:latest
ports:
- "1081:1080"
- "127.0.0.1:1081:1080"
garage:
user: ${DOCKER_USER:-1000}
@@ -69,7 +71,7 @@ services:
- env.d/development/common
- env.d/development/postgresql
ports:
- "8071:8000"
- "127.0.0.1:8071:8000"
volumes:
- ./src/backend:/app
- ./data/static:/data/static
@@ -135,7 +137,7 @@ services:
nginx:
image: nginx:1.25
ports:
- "8083:8083"
- "127.0.0.1:8083:8083"
volumes:
- ./docker/files/etc/nginx/conf.d:/etc/nginx/conf.d:ro
depends_on:
@@ -153,10 +155,11 @@ services:
target: frontend-production
args:
VITE_API_BASE_URL: "http://localhost:8071"
VITE_MEDIA_BASE_URL: "http://localhost:8083"
VITE_APP_TITLE: "LaSuite Meet"
image: meet:frontend-development
ports:
- "3000:8080"
- "127.0.0.1:3000:8080"
dockerize:
image: jwilder/dockerize
@@ -172,7 +175,7 @@ services:
working_dir: /app
node:
image: node:22
image: node:22.23.4-alpine
user: "${DOCKER_USER:-1000}"
environment:
HOME: /tmp
@@ -182,7 +185,7 @@ services:
kc_postgresql:
image: postgres:14.3
ports:
- "5433:5432"
- "127.0.0.1:5433:5432"
env_file:
- env.d/development/kc_postgresql
@@ -210,19 +213,19 @@ services:
KC_DB_SCHEMA: public
PROXY_ADDRESS_FORWARDING: 'true'
ports:
- "8080:8080"
- "127.0.0.1:8080:8080"
depends_on:
- kc_postgresql
livekit:
image: livekit/livekit-server:v1.13.6
image: livekit/livekit-server:v1.13.11
entrypoint: /livekit-server --dev --bind 0.0.0.0 --config ./config.yaml
ports:
- "7880:7880"
- "7881:7881"
- "7882:7882/udp"
- "3478:3478/udp"
- "30000-30100:30000-30100/udp"
- "127.0.0.1:7881:7881"
- "127.0.0.1:7882:7882/udp"
- "127.0.0.1:3478:3478/udp"
- "127.0.0.1:30000-30100:30000-30100/udp"
volumes:
- ./docker/livekit/config/livekit-server.yaml:/config.yaml
depends_on:
@@ -230,7 +233,7 @@ services:
- livekit-egress
livekit-egress:
image: livekit/egress:v1.11.0
image: livekit/egress:v1.15.0
environment:
EGRESS_CONFIG_FILE: ./livekit-egress.yaml
volumes:
@@ -270,11 +273,6 @@ services:
- ./src/agents:/app
- /app/.venv
redis-summary:
image: redis
ports:
- "6379:6379"
app-summary-dev:
build:
context: src/summary
@@ -285,11 +283,11 @@ services:
env_file:
- env.d/development/summary
ports:
- "8001:8000"
- "127.0.0.1:8001:8000"
volumes:
- ./src/summary:/app
depends_on:
- redis-summary
- redis
celery-summary-transcribe:
container_name: celery-summary-transcribe
@@ -303,7 +301,7 @@ services:
volumes:
- ./src/summary:/app
depends_on:
- redis-summary
- redis
- app-summary-dev
- garage
develop:
@@ -323,7 +321,7 @@ services:
volumes:
- ./src/summary:/app
depends_on:
- redis-summary
- redis
- app-summary-dev
- garage
develop:
+12
View File
@@ -38,6 +38,17 @@ server {
add_header Cache-Control "public, max-age=2592000";
}
location = / {
try_files /home.html /index.html;
add_header Cache-Control "no-cache, no-store, must-revalidate";
add_header Pragma "no-cache";
add_header Expires 0;
}
location = /home.html {
internal;
}
# Serve static files
location / {
try_files $uri $uri/ /index.html;
@@ -45,6 +56,7 @@ server {
add_header Cache-Control "no-cache, no-store, must-revalidate";
add_header Pragma "no-cache"; # HTTP 1.0 header for backward compatibility
add_header Expires 0;
add_header X-Robots-Tag "noindex, nofollow" always;
}
# Optionally, handle 404 errors by redirecting to index.html
+42 -3
View File
@@ -18,12 +18,50 @@
"url": "https://github.com/cachix/devenv"
}
},
"flake-compat": {
"flake": false,
"locked": {
"lastModified": 1767039857,
"narHash": "sha256-vNpUSpF5Nuw8xvDLj2KCwwksIbjua2LZCqhV1LNRDns=",
"owner": "NixOS",
"repo": "flake-compat",
"rev": "5edf11c44bc78a0d334f6334cdaf7d60d732daab",
"type": "github"
},
"original": {
"owner": "NixOS",
"repo": "flake-compat",
"type": "github"
}
},
"git-hooks": {
"inputs": {
"flake-compat": "flake-compat",
"nixpkgs": [
"nixpkgs"
]
},
"locked": {
"lastModified": 1791909798,
"narHash": "sha256-VAhpCOmrun/KXimYfR8NM88bciKCui7CqHHhThSzgag=",
"ref": "refs/heads/master",
"rev": "1ba1dbfe28738c9a71c266be6efa5b89e75491a9",
"shallow": true,
"type": "git",
"url": "https://github.com/cachix/git-hooks.nix"
},
"original": {
"shallow": true,
"type": "git",
"url": "https://github.com/cachix/git-hooks.nix"
}
},
"nixpkgs": {
"locked": {
"lastModified": 1789542786,
"narHash": "sha256-ajQuqcxnj6RYnwCjA/9FTCnrdR2+BDzstE8UembXf60=",
"lastModified": 1792295010,
"narHash": "sha256-F7meJtbqGttmUoMmYjRRgkVs42sn7bh7vvRvLPlUN98=",
"ref": "nixos-26.05",
"rev": "4c7870105e7f1fdf9c48688c8d7efc21abf0688a",
"rev": "8ce73368d1efd4d657e9064d29b144a52046b4e8",
"shallow": true,
"type": "git",
"url": "https://github.com/NixOS/nixpkgs"
@@ -38,6 +76,7 @@
"root": {
"inputs": {
"devenv": "devenv",
"git-hooks": "git-hooks",
"nixpkgs": "nixpkgs"
}
}
+2
View File
@@ -101,6 +101,8 @@ in
languages.typescript.enable = false;
languages.nix.enable = true;
git-hooks.hooks.gitlint.enable = true;
packages =
with pkgs;
[
+5
View File
@@ -3,3 +3,8 @@ inputs:
url: git+https://github.com/NixOS/nixpkgs?ref=nixos-26.05&shallow=1
devenv:
url: git+https://github.com/cachix/devenv?ref=refs/tags/v2.1.2&dir=src/modules
git-hooks:
url: git+https://github.com/cachix/git-hooks.nix?shallow=1
inputs:
nixpkgs:
follows: nixpkgs
+1 -1
View File
@@ -45,4 +45,4 @@ services:
# The local proxy listens on 8080 and collides with Keycloak's published admin port.
keycloak:
ports: !override
- "8081:8080"
- "127.0.0.1:8081:8080"
+9 -7
View File
@@ -1,5 +1,7 @@
# ---- Front-end image ----
FROM node:22-alpine AS frontend-deps
FROM --platform=$BUILDPLATFORM node:22.23.4-alpine AS frontend-deps
RUN apk upgrade --no-cache ca-certificates
WORKDIR /home/frontend/
@@ -39,7 +41,9 @@ COPY ./docker/dinum-frontend/fonts/ \
./dist/assets/fonts/
# ---- Addons builder image ----
FROM node:20-alpine AS addons-builder
FROM --platform=$BUILDPLATFORM node:22.23.4-alpine AS addons-builder
RUN apk upgrade --no-cache ca-certificates
WORKDIR /home/addons/outlook
@@ -54,13 +58,11 @@ RUN npx webpack --mode production
# ---- Front-end image ----
FROM nginxinc/nginx-unprivileged:1.30.4-alpine3.24 AS frontend-production
FROM nginx/nginx-unprivileged:1.30.6-alpine3.24 AS frontend-production
USER root
RUN apk upgrade --no-cache libexpat && \
apk del curl
USER nginx
RUN apk del curl && \
rm -f /usr/share/nginx/html/50x.html
USER nginx
# Un-privileged user running the application
+13
View File
@@ -43,6 +43,7 @@ server {
add_header Cache-Control "no-cache, no-store, must-revalidate";
add_header Pragma "no-cache" always;
add_header Expires 0 always;
add_header X-Robots-Tag "noindex, nofollow" always;
set $ms_domains "https://*.live.com https://*.office.com https://*.microsoft.com https://*.office365.com https://*.sharepoint.com";
@@ -76,6 +77,17 @@ server {
add_header Cache-Control "public, max-age=2592000";
}
location = / {
try_files /home.html /index.html;
add_header Cache-Control "no-cache, no-store, must-revalidate";
add_header Pragma "no-cache";
add_header Expires 0;
}
location = /home.html {
internal;
}
# Serve static files
location / {
try_files $uri $uri/ /index.html;
@@ -83,6 +95,7 @@ server {
add_header Cache-Control "no-cache, no-store, must-revalidate";
add_header Pragma "no-cache"; # HTTP 1.0 header for backward compatibility
add_header Expires 0;
add_header X-Robots-Tag "noindex, nofollow" always;
}
# Optionally, handle 404 errors by redirecting to index.html
@@ -4,6 +4,36 @@ server {
server_name localhost;
charset utf-8;
# Proxy auth for recordings (authorized by the recordings viewset)
location /media/recordings/ {
auth_request /media-auth-recordings;
auth_request_set $authHeader $upstream_http_authorization;
auth_request_set $authDate $upstream_http_x_amz_date;
auth_request_set $authContentSha256 $upstream_http_x_amz_content_sha256;
proxy_set_header Authorization $authHeader;
proxy_set_header X-Amz-Date $authDate;
proxy_set_header X-Amz-Content-SHA256 $authContentSha256;
proxy_pass http://garage:9000/meet-media-storage/recordings/;
proxy_set_header Host garage:9000;
proxy_hide_header Content-Disposition;
add_header Content-Disposition "attachment";
}
location = /media-auth-recordings {
internal;
proxy_pass http://app-dev:8000/api/v1.0/recordings/media-auth/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Original-URL $request_uri;
proxy_pass_request_body off;
proxy_set_header Content-Length "";
proxy_set_header X-Original-Method $request_method;
}
# Proxy auth for media
location /media/ {
# Auth request configuration
+4 -1
View File
@@ -14,4 +14,7 @@ accesslog = "-"
# Using '-' for the error log file makes gunicorn log errors to stderr
errorlog = "-"
loglevel = "info"
access_log_format = '%(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s" %(M)s'
access_log_format = (
'%(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s" %(M)s'
" rid=%({x-request-id}o)s"
)
+1 -1
View File
@@ -1,4 +1,4 @@
FROM livekit/livekit-server:v1.13.6
FROM livekit/livekit-server:v1.13.11
# We inject the nip.io certificate manually because the livekit chart doesn't support volume mounting
COPY rootCA.pem /etc/ssl/certs/
+2 -1
View File
@@ -1,4 +1,5 @@
log_level: debug
logging:
level: debug
api_key: devkey
api_secret: secret
ws_url: "ws://livekit:7880"
@@ -4,6 +4,12 @@ redis:
keys:
devkey: secret
# The backend creates rooms before it hands out a join token, so LiveKit must not
# create them on join. This also lets Meet share its LiveKit instance with
# services that require this setting.
room:
auto_create: false
webhook:
api_key: devkey
urls:
Binary file not shown.

After

Width:  |  Height:  |  Size: 87 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 200 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.2 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.1 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.0 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 473 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 769 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 861 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 228 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 75 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 218 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 146 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M12 14V16C8.68629 16 6 18.6863 6 22H4C4 17.5817 7.58172 14 12 14ZM12 13C8.685 13 6 10.315 6 7C6 3.685 8.685 1 12 1C15.315 1 18 3.685 18 7C18 10.315 15.315 13 12 13ZM12 11C14.21 11 16 9.21 16 7C16 4.79 14.21 3 12 3C9.79 3 8 4.79 8 7C8 9.21 9.79 11 12 11ZM21 17H22V22H14V17H15V16C15 14.3431 16.3431 13 18 13C19.6569 13 21 14.3431 21 16V17ZM19 17V16C19 15.4477 18.5523 15 18 15C17.4477 15 17 15.4477 17 16V17H19Z"/></svg>

After

Width:  |  Height:  |  Size: 507 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M13.0001 7.82843V20H11.0001V7.82843L5.63614 13.1924L4.22192 11.7782L12.0001 4L19.7783 11.7782L18.3641 13.1924L13.0001 7.82843Z"/></svg>

After

Width:  |  Height:  |  Size: 224 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M11.9999 10.8284L7.0502 15.7782L5.63599 14.364L11.9999 8L18.3639 14.364L16.9497 15.7782L11.9999 10.8284Z"/></svg>

After

Width:  |  Height:  |  Size: 202 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M10 3H14C18.4183 3 22 6.58172 22 11C22 15.4183 18.4183 19 14 19V22.5C9 20.5 2 17.5 2 11C2 6.58172 5.58172 3 10 3ZM12 17H14C17.3137 17 20 14.3137 20 11C20 7.68629 17.3137 5 14 5H10C6.68629 5 4 7.68629 4 11C4 14.61 6.46208 16.9656 12 19.4798V17Z"/></svg>

After

Width:  |  Height:  |  Size: 341 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M11.9997 10.5865L16.9495 5.63672L18.3637 7.05093L13.4139 12.0007L18.3637 16.9504L16.9495 18.3646L11.9997 13.4149L7.04996 18.3646L5.63574 16.9504L10.5855 12.0007L5.63574 7.05093L7.04996 5.63672L11.9997 10.5865Z"/></svg>

After

Width:  |  Height:  |  Size: 307 B

@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M21 3C21.5523 3 22 3.44772 22 4V20C22 20.5523 21.5523 21 21 21H3C2.44772 21 2 20.5523 2 20V4C2 3.44772 2.44772 3 3 3H21ZM20 5H4V19H20V5ZM9 8C10.1045 8 11.1049 8.44841 11.829 9.173L10.4153 10.5866C10.0534 10.2241 9.55299 10 9 10C7.895 10 7 10.895 7 12C7 13.105 7.895 14 9 14C9.5525 14 10.0525 13.7762 10.4144 13.4144L11.828 14.828C11.104 15.552 10.104 16 9 16C6.792 16 5 14.208 5 12C5 9.792 6.792 8 9 8ZM16 8C17.1045 8 18.1049 8.44841 18.829 9.173L17.4153 10.5866C17.0534 10.2241 16.553 10 16 10C14.895 10 14 10.895 14 12C14 13.105 14.895 14 16 14C16.5525 14 17.0525 13.7762 17.4144 13.4144L18.828 14.828C18.104 15.552 17.104 16 16 16C13.792 16 12 14.208 12 12C12 9.792 13.792 8 16 8Z"/></svg>

After

Width:  |  Height:  |  Size: 781 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M12 22C6.47715 22 2 17.5228 2 12C2 6.47715 6.47715 2 12 2C17.5228 2 22 6.47715 22 12C22 17.5228 17.5228 22 12 22ZM12 20C16.4183 20 20 16.4183 20 12C20 7.58172 16.4183 4 12 4C7.58172 4 4 7.58172 4 12C4 16.4183 7.58172 20 12 20ZM8 13H16C16 15.2091 14.2091 17 12 17C9.79086 17 8 15.2091 8 13ZM8 11C7.17157 11 6.5 10.3284 6.5 9.5C6.5 8.67157 7.17157 8 8 8C8.82843 8 9.5 8.67157 9.5 9.5C9.5 10.3284 8.82843 11 8 11ZM16 11C15.1716 11 14.5 10.3284 14.5 9.5C14.5 8.67157 15.1716 8 16 8C16.8284 8 17.5 8.67157 17.5 9.5C17.5 10.3284 16.8284 11 16 11Z"/></svg>

After

Width:  |  Height:  |  Size: 638 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M2 22C2 17.5817 5.58172 14 10 14C14.4183 14 18 17.5817 18 22H16C16 18.6863 13.3137 16 10 16C6.68629 16 4 18.6863 4 22H2ZM10 13C6.685 13 4 10.315 4 7C4 3.685 6.685 1 10 1C13.315 1 16 3.685 16 7C16 10.315 13.315 13 10 13ZM10 11C12.21 11 14 9.21 14 7C14 4.79 12.21 3 10 3C7.79 3 6 4.79 6 7C6 9.21 7.79 11 10 11ZM18.2837 14.7028C21.0644 15.9561 23 18.752 23 22H21C21 19.564 19.5483 17.4671 17.4628 16.5271L18.2837 14.7028ZM17.5962 3.41321C19.5944 4.23703 21 6.20361 21 8.5C21 11.3702 18.8042 13.7252 16 13.9776V11.9646C17.6967 11.7222 19 10.264 19 8.5C19 7.11935 18.2016 5.92603 17.041 5.35635L17.5962 3.41321Z"/></svg>

After

Width:  |  Height:  |  Size: 704 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M12.5002 2C12.2241 2 12.0002 2.22386 12.0002 2.5V12H10.0002V4.5C10.0002 4.22386 9.77634 4 9.5002 4C9.22405 4 9.0002 4.22386 9.0002 4.5V14C8.64653 14 7.00024 14 7.00024 14C6.61911 12.3792 5.64236 11.4407 4.5954 11.3216C4.87926 12.0664 5.36117 13.2592 6.16634 15.0995C7.02511 17.0622 7.89128 18.5218 9.00374 19.4986C10.0783 20.442 11.4586 21 13.5002 21C16.5378 21 19.0002 18.5377 19.0002 15.5002V7C19.0002 6.72386 18.7763 6.5 18.5002 6.5C18.2241 6.5 18.0002 6.72386 18.0002 7V12H16.0002V4C16.0002 3.72386 15.7763 3.5 15.5002 3.5C15.2241 3.5 15.0002 3.72386 15.0002 4V12H13.0002V2.5C13.0002 2.22386 12.7763 2 12.5002 2ZM21.0002 15.5002C21.0002 19.6424 17.6423 23 13.5002 23C11.0417 23 9.17214 22.308 7.68416 21.0015C6.23411 19.7283 5.22528 17.9381 4.33405 15.9012C3.40393 13.7753 2.89004 12.4804 2.60991 11.7235C2.25318 10.7597 2.74616 9.41212 4.08583 9.31846C5.24076 9.23771 6.22061 9.61249 7.0002 10.2587V4.5C7.0002 3.11929 8.11949 2 9.5002 2C9.68522 2 9.86554 2.0201 10.0391 2.05823C10.2477 0.888227 11.2702 0 12.5002 0C13.5602 0 14.4661 0.659694 14.8298 1.59091C15.0431 1.53167 15.268 1.5 15.5002 1.5C16.8809 1.5 18.0002 2.61929 18.0002 4V4.55001C18.1618 4.51722 18.329 4.5 18.5002 4.5C19.8809 4.5 21.0002 5.61929 21.0002 7V15.5002Z"/></svg>

After

Width:  |  Height:  |  Size: 1.3 KiB

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M12 22C6.47715 22 2 17.5228 2 12C2 6.47715 6.47715 2 12 2C17.5228 2 22 6.47715 22 12C22 17.5228 17.5228 22 12 22ZM12 20C16.4183 20 20 16.4183 20 12C20 7.58172 16.4183 4 12 4C7.58172 4 4 7.58172 4 12C4 16.4183 7.58172 20 12 20ZM11 7H13V9H11V7ZM11 11H13V17H11V11Z"/></svg>

After

Width:  |  Height:  |  Size: 359 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M11.9998 3C10.3429 3 8.99976 4.34315 8.99976 6V10C8.99976 11.6569 10.3429 13 11.9998 13C13.6566 13 14.9998 11.6569 14.9998 10V6C14.9998 4.34315 13.6566 3 11.9998 3ZM11.9998 1C14.7612 1 16.9998 3.23858 16.9998 6V10C16.9998 12.7614 14.7612 15 11.9998 15C9.23833 15 6.99976 12.7614 6.99976 10V6C6.99976 3.23858 9.23833 1 11.9998 1ZM3.05469 11H5.07065C5.55588 14.3923 8.47329 17 11.9998 17C15.5262 17 18.4436 14.3923 18.9289 11H20.9448C20.4837 15.1716 17.1714 18.4839 12.9998 18.9451V23H10.9998V18.9451C6.82814 18.4839 3.51584 15.1716 3.05469 11Z"/></svg>

After

Width:  |  Height:  |  Size: 640 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M16.4249 17.839L21.1925 22.6066L22.6068 21.1924L2.80777 1.3934L1.39355 2.80761L7.00016 8.41421V10C7.00016 12.7614 9.23873 15 12.0002 15C12.4825 15 12.9489 14.9317 13.3902 14.8042L14.9404 16.3544C14.0464 16.7688 13.0503 17 12.0002 17C8.47368 17 5.55627 14.3923 5.07105 11H3.05509C3.51623 15.1716 6.82854 18.4839 11.0002 18.9451V23H13.0002V18.9451C14.2341 18.8087 15.3929 18.4228 16.4249 17.839ZM11.5528 12.9669C10.2541 12.7727 9.22745 11.7461 9.03328 10.4473L11.5528 12.9669ZM19.3747 15.1604L17.9323 13.7179C18.4407 12.9084 18.788 11.9874 18.9293 11H20.9452C20.7754 12.5366 20.2187 13.9565 19.3747 15.1604ZM16.4658 12.2514L14.9173 10.703C14.9715 10.4775 15.0002 10.2421 15.0002 10V6C15.0002 4.34315 13.657 3 12.0002 3C10.7059 3 9.6031 3.81956 9.18237 4.96802L7.68575 3.47139C8.55427 1.99268 10.1613 1 12.0002 1C14.7616 1 17.0002 3.23858 17.0002 6V10C17.0002 10.8099 16.8076 11.5748 16.4658 12.2514Z"/></svg>

After

Width:  |  Height:  |  Size: 995 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M5 10C3.9 10 3 10.9 3 12C3 13.1 3.9 14 5 14C6.1 14 7 13.1 7 12C7 10.9 6.1 10 5 10ZM19 10C17.9 10 17 10.9 17 12C17 13.1 17.9 14 19 14C20.1 14 21 13.1 21 12C21 10.9 20.1 10 19 10ZM12 10C10.9 10 10 10.9 10 12C10 13.1 10.9 14 12 14C13.1 14 14 13.1 14 12C14 10.9 13.1 10 12 10Z"/></svg>

After

Width:  |  Height:  |  Size: 370 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M21 16.42V19.9561C21 20.4811 20.5941 20.9167 20.0705 20.9537C19.6331 20.9846 19.2763 21 19 21C10.1634 21 3 13.8366 3 5C3 4.72371 3.01545 4.36687 3.04635 3.9295C3.08337 3.40588 3.51894 3 4.04386 3H7.5801C7.83678 3 8.05176 3.19442 8.07753 3.4498C8.10067 3.67907 8.12218 3.86314 8.14207 4.00202C8.34435 5.41472 8.75753 6.75936 9.3487 8.00303C9.44359 8.20265 9.38171 8.44159 9.20185 8.57006L7.04355 10.1118C8.35752 13.1811 10.8189 15.6425 13.8882 16.9565L15.4271 14.8019C15.5572 14.6199 15.799 14.5573 16.001 14.6532C17.2446 15.2439 18.5891 15.6566 20.0016 15.8584C20.1396 15.8782 20.3225 15.8995 20.5502 15.9225C20.8056 15.9483 21 16.1633 21 16.42Z"/></svg>

After

Width:  |  Height:  |  Size: 743 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M3 4H21C21.5523 4 22 4.44772 22 5V19C22 19.5523 21.5523 20 21 20H3C2.44772 20 2 19.5523 2 19V5C2 4.44772 2.44772 4 3 4ZM4 6V18H20V6H4Z"/></svg>

After

Width:  |  Height:  |  Size: 232 B

+4
View File
@@ -0,0 +1,4 @@
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="20" height="20">
<path d="M3 3H21C21.5523 3 22 3.44772 22 4V16C22 16.5523 21.5523 17 21 17H3C2.44772 17 2 16.5523 2 16V4C2 3.44772 2.44772 3 3 3ZM4 5V15H20V5H4Z" fill="currentColor"/>
<path d="M12 7.58578L16.9497 12.5355L15.5355 13.9497L13 11.4142L13 17H11L11 11.4142L8.46447 13.9497L7.05025 12.5355L12 7.58578Z" fill="currentColor"/>
</svg>

After

Width:  |  Height:  |  Size: 413 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M11.9998 1L6 11H18L11.9998 1ZM11.9998 4.8873L14.4676 9H9.53232L11.9998 4.8873ZM6.75 20C5.23122 20 4 18.7688 4 17.25C4 15.7312 5.23122 14.5 6.75 14.5C8.26878 14.5 9.5 15.7312 9.5 17.25C9.5 18.7688 8.26878 20 6.75 20ZM6.75 22C9.37335 22 11.5 19.8734 11.5 17.25C11.5 14.6266 9.37335 12.5 6.75 12.5C4.12665 12.5 2 14.6266 2 17.25C2 19.8734 4.12665 22 6.75 22ZM15 15.5V19.5H19V15.5H15ZM13 21.5V13.5H21V21.5H13Z"/></svg>

After

Width:  |  Height:  |  Size: 503 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M17 18.4142L21.1925 22.6067L22.6067 21.1925L2.80769 1.39349L1.39348 2.80771L2.58579 4.00001H2C1.44772 4.00001 1 4.44773 1 5.00001V19C1 19.5523 1.44772 20 2 20H16C16.5523 20 17 19.5523 17 19V18.4142ZM15 16.4142V18H3V6.00001H4.58579L15 16.4142ZM23 18.0397C23 18.2517 22.875 18.4176 22.7083 18.4943L21 16.786V8.84133L17 11.6413V12.786L15 10.786V6.00001H10.214L8.21402 4.00001H16C16.5523 4.00001 17 4.44773 17 5.00001V9.20001L22.2133 5.55073C22.5447 5.31876 23 5.55583 23 5.96034V18.0397Z"/></svg>

After

Width:  |  Height:  |  Size: 582 B

+1
View File
@@ -0,0 +1 @@
<svg viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg"><path d="M17 9.2L22.2133 5.55071C22.4395 5.39235 22.7513 5.44737 22.9096 5.6736C22.9684 5.75764 23 5.85774 23 5.96033V18.0397C23 18.3158 22.7761 18.5397 22.5 18.5397C22.3974 18.5397 22.2973 18.5081 22.2133 18.4493L17 14.8V19C17 19.5523 16.5523 20 16 20H2C1.44772 20 1 19.5523 1 19V5C1 4.44772 1.44772 4 2 4H16C16.5523 4 17 4.44772 17 5V9.2ZM17 12.3587L21 15.1587V8.84131L17 11.6413V12.3587ZM3 6V18H15V6H3Z"/></svg>

After

Width:  |  Height:  |  Size: 494 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 294 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 177 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 295 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 230 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 942 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 548 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

+224
View File
@@ -0,0 +1,224 @@
#!/bin/bash
# check-install.sh - Check a LaSuite Meet install on Docker Compose
#
# Prints the setup it finds, then one line per check: ✓ when it passes, ✗ and
# the cause when it fails. Exits 0 only when every check passed.
#
# Run it on the server, in the Meet stack's directory, as the user who runs
# docker compose:
# cd ~/docker/meet && curl -fsSL https://raw.githubusercontent.com/suitenumerique/meet/main/docs/check-install.sh | bash
#
# It reads the domains from the .env there, and checks the Keycloak stack too
# when ../keycloak exists. It needs bash, docker and curl.
set -euo pipefail
KC_DIR="$(dirname "$PWD")/keycloak"
die() { echo "Error: $*" >&2; exit 1; }
command -v docker >/dev/null 2>&1 || die "docker is not installed."
command -v curl >/dev/null 2>&1 || die "curl is not installed."
[[ -f .env ]] || die "No .env in $PWD. Run this in the Meet stack's directory, ~/docker/meet."
# env_value KEY: the value of KEY in the stack's .env, empty when it has none.
env_value() {
local key="$1"
grep -E "^${key}=" .env | tail -1 | cut -d= -f2- | tr -d "\"'" || true
}
MEET_HOST=$(env_value MEET_HOST)
LIVEKIT_HOST=$(env_value LIVEKIT_HOST)
IDP_HOST=$(env_value IDP_HOST)
REALM_NAME=$(env_value REALM_NAME)
COMPOSE_PROFILES=$(env_value COMPOSE_PROFILES)
[[ -n "$MEET_HOST" && -n "$LIVEKIT_HOST" ]] \
|| die "MEET_HOST or LIVEKIT_HOST is missing from $PWD/.env."
if [[ -t 1 ]]; then OK=$'\e[32m✓\e[0m'; KO=$'\e[31m✗\e[0m'; else OK='✓'; KO='✗'; fi
tmp=$(mktemp)
trap 'rm -f "$tmp"' EXIT
passed=0
failed=0
pass() { echo " $OK $*"; passed=$((passed + 1)); }
fail() { echo " $KO $*"; failed=$((failed + 1)); }
skip() { echo " - $*"; }
# fetch URL: sets code and location, and why to curl's error when it got no answer.
fetch() {
local out
out=$(curl -sS --max-time 10 -o /dev/null -w '%{http_code} %{redirect_url}' "$1" 2>"$tmp") || true
code=${out%% *}
location=${out#* }
why=$(sed -n '1s/^curl: ([0-9]*) //p' "$tmp")
}
# check_stack NAME DIR: every service of the stack runs, and passes its health check.
check_stack() {
local name="$1" dir="$2" services states svc state health problems="" count=0
if ! services=$(cd "$dir" && docker compose config --services 2>"$tmp"); then
fail "$name stack: $(tail -1 "$tmp")"
return
fi
states=$(cd "$dir" && docker compose ps --all --format '{{.Service}} {{.State}} {{.Health}}' 2>/dev/null)
for svc in $services; do
count=$((count + 1))
read -r _ state health <<<"$(grep "^$svc " <<<"$states" || true)"
if [[ -z "${state:-}" ]]; then
problems+=", $svc not created"
elif [[ "$state" != running ]]; then
problems+=", $svc $state"
elif [[ -n "${health:-}" && "$health" != healthy ]]; then
problems+=", $svc $health"
fi
done
if [[ -z "$problems" ]]; then
pass "$name stack: $count services running, health checks passing"
else
fail "$name stack: ${problems#, }"
fi
}
# ── Your setup ────────────────────────────────────────────────────────────────
version="unknown, the backend is not running"
backend_id=$(docker compose ps -q backend 2>/dev/null || true)
if [[ -n "$backend_id" ]]; then
read -r image version <<<"$(docker inspect --format \
'{{.Config.Image}} {{index .Config.Labels "org.opencontainers.image.version"}}' "$backend_id")"
version="${version/<no value>/unknown} (image ${image})"
fi
config=$(curl -sS --max-time 10 --fail "https://${MEET_HOST}/api/v1.0/config/" 2>"$tmp") || true
config_why=$(sed -n '1s/^curl: ([0-9]*) //p' "$tmp")
if [[ -n "$config" && "$config" != *'"livekit"'* ]]; then
config=""
config_why="the answer is not Meet's configuration"
fi
features=""
grep -qE '"recording": *\{ *"is_enabled": *true' <<<"$config" && features+=", recording"
grep -qE '"subtitle": *\{ *"enabled": *true' <<<"$config" && features+=", subtitles"
grep -qE '"telephony": *\{ *"enabled": *true' <<<"$config" && features+=", telephony"
grep -qE '"connection_test_enabled": *true' <<<"$config" && features+=", connection test"
if [[ -z "$config" ]]; then
features="unknown, the configuration did not load"
else
features=${features#, }
fi
echo "Your setup"
echo " Version ${version}"
echo " Meet ${MEET_HOST}"
echo " LiveKit ${LIVEKIT_HOST}"
echo " Sign-in ${IDP_HOST:-not set}"
echo " Profiles ${COMPOSE_PROFILES:-none}"
echo " Features ${features:-none turned on}"
echo ""
echo "Checks"
# ── 1. Services ───────────────────────────────────────────────────────────────
check_stack Meet "$PWD"
[[ -d "$KC_DIR" ]] && check_stack Keycloak "$KC_DIR"
# ── 2. The backend's own production checks ────────────────────────────────────
# Piped into bash, this script is stdin: docker must not read it.
if out=$(docker compose exec -T backend python manage.py check --deploy </dev/null 2>&1); then
pass "Backend: manage.py check --deploy passes"
else
issue=$(grep -m1 -E '\.E[0-9]+\)' <<<"$out" || grep -v '^\s*$' <<<"$out" | tail -1)
fail "Backend: ${issue}"
fi
# ── 3. Each domain answers over HTTPS ─────────────────────────────────────────
urls=("https://${MEET_HOST}/" "https://${LIVEKIT_HOST}/")
[[ -d "$KC_DIR" ]] && urls+=("https://${IDP_HOST}/realms/${REALM_NAME:-meet}")
for url in "${urls[@]}"; do
fetch "$url"
if [[ "$code" == 200 ]]; then
pass "$url answers 200, certificate valid"
elif [[ "$code" == 000 ]]; then
fail "$url: $why"
else
fail "$url answers $code, not 200"
fi
done
# ── 4. Browsers get LiveKit's public address ──────────────────────────────────
livekit_url=$(grep -oE '"livekit": *\{ *"url": *"[^"]*"' <<<"$config" | cut -d'"' -f6 || true)
if [[ -z "$config" ]]; then
fail "https://${MEET_HOST}/api/v1.0/config/: $config_why"
elif [[ "${livekit_url%/}" == "https://${LIVEKIT_HOST}" ]]; then
pass "Meet sends browsers to LiveKit at ${livekit_url}"
else
fail "Meet sends browsers to LiveKit at ${livekit_url:-no address}, not https://${LIVEKIT_HOST}: set LIVEKIT_API_URL"
fi
# ── 5. Sign-in leaves for the identity provider ───────────────────────────────
fetch "https://${MEET_HOST}/api/v1.0/authenticate/"
idp=$(sed -E 's|^[a-z]+://([^/:?]*).*|\1|' <<<"$location")
if [[ "$code" == 302 && -n "$location" && "$idp" != "$MEET_HOST" ]]; then
pass "Sign-in sends browsers to ${idp}"
elif [[ "$code" == 000 ]]; then
fail "Sign-in: $why"
elif [[ "$code" == 302 ]]; then
fail "Sign-in sends browsers to ${location%%\?*}, not to the identity provider"
else
fail "Sign-in: /api/v1.0/authenticate/ answers $code, not 302"
fi
# ── 6. LiveKit announces the address its domain resolves to ───────────────────
node_ip=$(docker compose logs livekit 2>/dev/null | grep -o '"nodeIP": "[^"]*"' | tail -1 | cut -d'"' -f4 || true)
addresses=$(getent ahosts "$LIVEKIT_HOST" | cut -d' ' -f1 | sort -u || true)
if [[ -z "$addresses" ]]; then
fail "${LIVEKIT_HOST} does not resolve from this server"
elif [[ -z "$node_ip" ]]; then
fail "LiveKit's log has no nodeIP line"
elif grep -qxF "$node_ip" <<<"$addresses"; then
pass "LiveKit announces ${node_ip}, the address of ${LIVEKIT_HOST}"
else
fail "LiveKit announces ${node_ip}, but ${LIVEKIT_HOST} resolves to ${addresses//$'\n'/ }"
fi
# Prefer the address LiveKit announces, which browsers send media to.
target=$(grep -xF "${node_ip:-none}" <<<"$addresses" || head -1 <<<"$addresses")
if [[ -z "$target" ]]; then
fail "${LIVEKIT_HOST}:7881 untested, the domain does not resolve"
elif timeout 5 bash -c "exec 3<>/dev/tcp/${target}/7881" 2>/dev/null; then
pass "${LIVEKIT_HOST}:7881 accepts TCP from this server; a test from outside is stronger"
else
fail "${LIVEKIT_HOST}:7881 does not accept TCP from this server: open the port in the firewall"
fi
# ── 7. LiveKit reports calls to the backend ───────────────────────────────────
codes=$(docker compose logs backend 2>/dev/null \
| grep -oE 'webhooks-livekit/[^"]*" [0-9]{3}' | grep -oE '[0-9]{3}$' || true)
if [[ -z "$codes" ]]; then
skip "LiveKit webhooks: no call yet"
else
total=$(wc -l <<<"$codes")
bad=$(grep -cvx 200 <<<"$codes" || true)
if [[ "$bad" == 0 ]]; then
pass "LiveKit webhooks: all ${total} answered 200"
else
fail "LiveKit webhooks: ${bad} of ${total} answered $(grep -vx 200 <<<"$codes" | sort -u | paste -sd,)"
fi
fi
# ── Verdict ───────────────────────────────────────────────────────────────────
echo ""
if [[ "$failed" == 0 ]]; then
echo "All $((passed + failed)) checks passed. Now join a meeting from two devices on different networks."
else
echo "${failed} of $((passed + failed)) checks failed."
exit 1
fi
+321
View File
@@ -0,0 +1,321 @@
# Code tour
Find each part of Meet's code in the repository before you change it. [How Meet works](../overview/how-meet-works.md) explains how the parts work together, and [Develop locally](develop.md) how to run them.
## TL;DR
The Django backend is [`src/backend`](https://github.com/suitenumerique/meet/tree/main/src/backend), the React frontend [`src/frontend`](https://github.com/suitenumerique/meet/tree/main/src/frontend), and LiveKit carries the media. The agents, the summary service and the Helm chart each have their own directory under `src/`.
## The repository
```
meet/
├── src/
│ ├── backend/ Django application: API, rooms, recordings, LiveKit control
│ ├── frontend/ React application served to browsers
│ ├── agents/ LiveKit agents: live subtitles, metadata collector
│ ├── summary/ FastAPI service that transcribes and summarizes recordings
│ ├── sdk/ TypeScript SDK: a button that creates a Meet link in another app
│ ├── addons/ Outlook add-in
│ ├── mail/ MJML sources of the emails
│ └── helm/ Helm chart and the helmfile used for local Kubernetes
├── .github/ CI: pull request checks, image builds, Helm chart release
├── docker/ Dev Keycloak realm, LiveKit, nginx, Garage; DINUM frontend image
├── env.d/ Environment file templates, for development and production
├── bin/ Wrappers for docker compose, Tiltfile, release, Scalingo buildpack
├── deploy/ The nginx configuration template of the Scalingo deployment
├── crowdin/ The Crowdin configuration that syncs the translations
├── docs/ This site
├── gitlint/ The commit message rule CI applies
├── compose.yml The development stack
├── Dockerfile The backend image, development and production stages
├── Makefile Every development command
├── CHANGELOG.md One line per change, written in each pull request
└── UPGRADE.md What an operator does when upgrading
```
## Backend
A [Django](https://www.djangoproject.com/) 5.2 project in three parts:
- [`meet`](https://github.com/suitenumerique/meet/tree/main/src/backend/meet), the project, holds the settings and the root URLs.
- [`core`](https://github.com/suitenumerique/meet/tree/main/src/backend/core), an app, holds the code.
- [`demo`](https://github.com/suitenumerique/meet/tree/main/src/backend/demo), a second app, holds the `create_demo` and `createsuperuser` commands that `make demo` and `make superuser` call.
| Path under `src/backend/` | What it holds |
|---|---|
| [`meet/settings.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/meet/settings.py) | Every setting, read from environment variables through django-configurations; each variable is in [Environment variables](../reference/env-variables.md). [`DJANGO_CONFIGURATION`](../reference/env-variables.md#DJANGO_CONFIGURATION) picks the class: `Development` or `Test` locally, `Production` on a server |
| [`meet/celery_app.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/meet/celery_app.py) | The Celery application the `celery-dev` worker runs |
| [`core/models.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/models.py) | The data model, described under [Models](#models) |
| [`core/api/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/api) | The REST API the frontend calls, under `/api/v1.0/`, built on [Django REST Framework](https://www.django-rest-framework.org/): viewsets, serializers, permissions, throttling |
| [`core/external_api/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/external_api) | The API other applications call to create and manage rooms, authenticated with application tokens |
| [`core/addons/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/addons) | The endpoints of add-ins embedded in other applications, such as the Outlook add-in |
| [`core/authentication/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/authentication) | Sign-in, and the authentication of requests carrying a LiveKit pass |
| [`core/services/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/services) | The logic behind the API: the waiting room, presence, invitations, moderation, LiveKit webhooks, phone dial-in, subtitles |
| [`core/recording/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/recording) | Starting and stopping recordings, and what happens once one ends |
| [`core/tasks/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/tasks) | Celery tasks: deleting connection-test rooms, deleting files, sending email. They run on the Celery worker when [`CELERY_ENABLED`](../reference/env-variables.md#CELERY_ENABLED) is on. Otherwise file deletion and email run inline in the request, and the connection-test room cleanup is not scheduled |
| [`core/management/commands/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/management/commands) | Maintenance commands: `purge_deleted_files`, `purge_inactive_rooms`, `clean_pending_files` and `merge_duplicate_users` |
| [`core/audit/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/audit), [`core/auditing.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/auditing.py) | The audit log of room, token and recording operations, see [The audit log](#the-audit-log) |
| [`core/roomkit/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/roomkit) | Meeting-room hardware joining over SIP |
| [`core/analytics/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/analytics) | Product analytics sent to PostHog, and the feature flags read from it |
| [`core/admin.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/admin.py) | The Django admin pages |
| [`core/factories.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/factories.py), [`core/tests/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/tests) | Test data factories and the test suite |
| [`locale/`](https://github.com/suitenumerique/meet/tree/main/src/backend/locale) | The backend's translations |
Sign-in goes through the `oidc_login` module of [django-lasuite](https://github.com/suitenumerique/django-lasuite), built on mozilla-django-oidc; [`core/urls.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/urls.py) mounts its URLs. Meet's own backend class is in [`core/authentication/backends.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/authentication/backends.py).
### Models
| Model | What it stores |
|---|---|
| `User` | An account, created at the first OIDC sign-in. A staff account signs in to `/admin/` with its `admin_email` and a password |
| `Room` | A meeting room: its `slug`, the code in the URL; its `access_level`, `public`, `trusted` or `restricted`; its `configuration`, a JSON object every participant receives; and its telephony `pin_code` |
| `ResourceAccess` | A user's role on a room: `owner`, `administrator` or `member` |
| `Recording`, `RecordingAccess` | A recording or a transcription, its `status` from `initiated` to `saved` or a failure, and who may see it |
| `Application`, `ApplicationDomain` | An application allowed to call the external API, and the email domains it may act for |
| `File` | An uploaded file, such as a custom background image, and its upload state |
### API
[`core/urls.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/urls.py) mounts two APIs. The frontend's is described by the schema the backend generates, at `/api/v1.0/swagger/` under the `Development` configuration; the other is the [External API](../reference/external-api.md).
| API | Prefix | Routes and their code |
|---|---|---|
| Browser API | `/api/v1.0/` | `users`, `rooms`, `resource-accesses`, `recordings`, `files` and `diagnostics` from [`core/api/viewsets.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/api/viewsets.py); `roomkit` from `core/roomkit/`; `addons/sessions` from `core/addons/`; the sign-in routes; `config/`, the instance's settings for the frontend |
| External API | `/external-api/v1.0/`, mounted only when [`EXTERNAL_API_ENABLED`](../reference/env-variables.md#EXTERNAL_API_ENABLED) is on | `application`, `rooms` and `users` from [`core/external_api/viewsets.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/external_api/viewsets.py) |
Most actions on a room are extra routes of `RoomViewSet`, such as `request-entry`, `start-recording` or `mute-participant`.
## Frontend
A [React](https://react.dev/) 18 and [TypeScript](https://www.typescriptlang.org/) application built with [Vite](https://vite.dev/). Its libraries, whose versions are in [`package.json`](https://github.com/suitenumerique/meet/blob/main/src/frontend/package.json):
| For | Library |
|---|---|
| Components | [React Aria](https://react-spectrum.adobe.com/react-aria/) |
| Styles | [Panda CSS](https://panda-css.com/) |
| Global state | [Valtio](https://valtio.dev/) |
| Server data | [TanStack Query](https://tanstack.com/query) |
| Routes | [wouter](https://github.com/molefrog/wouter) |
| Translations | i18next |
| Calls | LiveKit's [`livekit-client`](https://github.com/livekit/client-sdk-js) and [`@livekit/components-react`](https://github.com/livekit/components-js) |
| Path under `src/frontend/src/` | What it holds |
|---|---|
| [`features/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/features) | One directory per feature: `rooms`, `chat`, `recording`, `participants`, `settings` and the others. Each keeps its own components, hooks and API calls |
| [`features/rooms/livekit/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/features/rooms/livekit) | Everything inside a call: the control bar, the participant tiles, the background effects, the LiveKit hooks |
| [`primitives/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/primitives) | The styled building blocks, `Button`, `ToggleButton`, `Dialog`, `Menu` and others, wrapping React Aria. A new component uses these rather than raw HTML or a direct React Aria import |
| [`components/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/components) | Components several features share |
| [`stores/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/stores) | Valtio stores, one file per concern: `layout.ts`, `chat.ts`, `recording.ts` and the others. A component reads one with `useSnapshot()` and changes it by assigning to the store |
| [`api/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/api) | `fetchApi`, which calls the backend, the TanStack Query client, and `useConfig`, which reads the instance's settings from `/api/v1.0/config/` |
| [`hooks/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/hooks) | Hooks shared across features, such as `useScreenReaderAnnounce` |
| [`locales/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/locales), [`i18n/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/i18n) | One JSON file per namespace and language, and the i18next setup |
| [`routes.ts`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/routes.ts) | The pages and their URLs |
| [`utils/livekit.ts`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/utils/livekit.ts) | Browser detection the LiveKit workarounds rely on |
Server data, such as a room or the list of recordings, goes through TanStack Query. A Valtio store holds what only the browser knows, such as the layout or an open panel.
Accessibility follows these patterns:
- Every interactive element has an accessible name, from its visible text or an `aria-label` read through `t()`. [`HandToggle.tsx`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/rooms/livekit/components/controls/HandToggle.tsx) shows the usual shape: a `ToggleButton` from the primitives, its label and tooltip translated.
- A state change the screen does not show, such as a recording starting, is announced with `useScreenReaderAnnounce()`.
- A room event goes through the toasts of [`ToastProvider.tsx`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/notifications/components/ToastProvider.tsx).
- A tooltip shown in picture-in-picture uses `VisualOnlyTooltip` instead of `TooltipWrapper`, so a screen reader does not read it twice. For the same reason, an element that only shows something carries no `aria-live`: announce the change once, with `useScreenReaderAnnounce()`.
- A React Aria `Dialog` traps focus and gives it back to the button that opened it. A side panel or a custom toolbar does neither: move focus into it yourself, with `autoFocus`, a `ref.focus()` or a `FocusScope`.
## How Meet talks to LiveKit
### The pass
The pass is the LiveKit access token the backend signs for each participant; the browser connects to LiveKit with it, as [Joining a meeting](../overview/how-meet-works.md#joining-a-meeting) describes.
Before issuing a pass, the backend makes sure the room exists in LiveKit, creating it with the room's configuration and access level as metadata. LiveKit is thus never asked to create a room on join, so its `room.auto_create` setting can stay `false`.
[`generate_token()`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/utils.py) in `core/utils.py` builds it. The token's name is the participant's display name, and it carries three attributes: `room_role`, `is_authenticated` and `color`, the last derived from the participant's identity.
Owners and administrators get LiveKit's `room_admin` grant, which lets them moderate.
The pass reaches the browser two ways:
- In the `livekit` field of the answer to `POST /api/v1.0/rooms/<id>/join/`, the `join` action of `RoomViewSet` in [`core/api/viewsets.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/api/viewsets.py), when the visitor may enter at once. The display name travels in its body, as `username`; reading a room returns no pass.
- In the answer to `POST /api/v1.0/rooms/<id>/request-entry/`, once someone admits the visitor from the waiting room, from [`core/services/lobby.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/lobby.py).
The pass also authenticates the API calls a participant makes during a call, signed in or not. They accept it through `LiveKitTokenAuthentication` in [`core/authentication/livekit.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/authentication/livekit.py).
```mermaid
sequenceDiagram
participant Browser
participant Backend
participant LiveKit
Browser->>Backend: POST /api/v1.0/rooms/{id}/join/ {username}
Backend->>LiveKit: Create the room if it does not exist
Backend-->>Browser: room, with livekit {url, token, room}
Browser->>LiveKit: WebSocket with the token
Browser->>LiveKit: publish microphone and camera
Backend->>LiveKit: room metadata, data messages, moderation, egress, agents
LiveKit->>Backend: POST /api/v1.0/rooms/webhooks-livekit/
```
### What the backend asks LiveKit
Every call goes through the client that [`create_livekit_client()`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/utils.py) returns.
| What | Backend side | What the frontend does with it |
|---|---|---|
| Creating a room before handing out a pass, and creating the rooms of unregistered links and connection tests | `RoomManagement.create_room()` and `ensure_room()` in [`core/services/room_management.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/room_management.py) | Nothing: the pass only works once the room exists |
| Room metadata: the room's configuration and access level, and the recording state | `RoomManagement.update_metadata()` in [`core/services/room_management.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/room_management.py) | [`RoomMetadataSynchronizer`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/rooms/livekit/components/RoomMetadataSynchronizer.tsx) copies the configuration and access level into the cached room, and [`useRecordingStatuses`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/recording/hooks/useRecordingStatuses.ts) reads the recording state |
| Data messages to every participant, such as someone waiting to enter | `notify_participants()` in [`core/utils.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/utils.py) | [`MainNotificationToast.tsx`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/notifications/MainNotificationToast.tsx) turns them into toasts and sounds |
| Muting, removing and updating a participant | [`core/services/participants_management.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/participants_management.py) | LiveKit applies it to the participant's connection |
| Recording, through LiveKit Egress | [`core/recording/worker/services.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/recording/worker/services.py), behind [`mediator.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/recording/worker/mediator.py) | Shows the state carried by the room metadata |
| Sending an agent into a room | [`core/services/subtitle.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/subtitle.py) for subtitles, [`core/recording/services/metadata_collector.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/recording/services/metadata_collector.py) during a transcription | Shows the subtitles the agent publishes |
| Phone dial-in rules, which route a caller's PIN to the room | [`core/services/sip_management.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/sip_management.py) | Nothing: the caller joins as an audio-only participant |
### What LiveKit tells the backend
LiveKit posts its events to `/api/v1.0/rooms/webhooks-livekit/`, the `webhooks_livekit` action of `RoomViewSet`. `LiveKitEventsService` in [`core/services/livekit_events.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/services/livekit_events.py) checks the signature, then handles each event:
| Event | What the backend does |
|---|---|
| `egress_updated` | Updates the recording's status |
| `egress_ended` | Clears the recording state from the room metadata and stops the metadata collector. On success, [`core/recording/event/notification.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/recording/event/notification.py) emails a screen recording's link to the people [Email](../self-hosting/configuration/email.md) names, and sends a transcription to the summary service |
| `room_started` | Closes the LiveKit room again if its Meet room was deleted; otherwise records the start time `purge_inactive_rooms` reads, and creates the room's phone dial-in rule when telephony or Roomkit is on |
| `room_finished` | Deletes that rule and clears the room's presence and waiting-room state |
| `participant_left` | Removes the participant from the presence cache, unless [`PRESENCE_CLEAR_ON_PARTICIPANT_LEFT`](../reference/env-variables.md#PRESENCE_CLEAR_ON_PARTICIPANT_LEFT) is off |
Any other event is acknowledged and ignored, and so is every event of a connection-test room or of a room whose name [`LIVEKIT_WEBHOOK_EVENTS_FILTER_REGEX`](../reference/env-variables.md#LIVEKIT_WEBHOOK_EVENTS_FILTER_REGEX) does not match. In development, LiveKit finds the endpoint through the `webhook` section of [`docker/livekit/config/livekit-server.yaml`](https://github.com/suitenumerique/meet/blob/main/docker/livekit/config/livekit-server.yaml).
### The frontend side
[`Conference.tsx`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/rooms/components/Conference.tsx) joins the room with `POST /api/v1.0/rooms/<id>/join/`, through [`joinRoom.ts`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/rooms/api/joinRoom.ts), builds the LiveKit `Room` with Meet's options, and renders `<LiveKitRoom>` with the pass and the server URL. When the answer carries no pass, it shows the waiting room instead. It also holds the browser workarounds, such as an early WebSocket that lets Firefox connect behind some proxies, when `enable_firefox_proxy_workaround` is on.
The call's interface is [`VideoConference.tsx`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/rooms/livekit/prefabs/VideoConference.tsx).
## Agents
[`src/agents`](https://github.com/suitenumerique/meet/tree/main/src/agents) holds two LiveKit agents, workers that LiveKit sends into a room as silent participants when the backend asks.
| File | What it does |
|---|---|
| [`multi_user_transcriber.py`](https://github.com/suitenumerique/meet/blob/main/src/agents/multi_user_transcriber.py) | Live subtitles: transcribes each speaker and publishes the text to the room |
| [`voxtral_vllm_stt.py`](https://github.com/suitenumerique/meet/blob/main/src/agents/voxtral_vllm_stt.py) | The speech-to-text plugin for Voxtral served by vLLM, one of the subtitles providers |
| [`metadata_collector.py`](https://github.com/suitenumerique/meet/blob/main/src/agents/metadata_collector.py) | During a transcription, records who speaks when, connections and chat, and writes them to S3 for the summary service |
Their settings are under [Agents](../reference/env-variables.md#agents).
## Summary service
[`src/summary`](https://github.com/suitenumerique/meet/tree/main/src/summary) is a [FastAPI](https://fastapi.tiangolo.com/) application with [Celery](https://docs.celeryq.dev/) workers:
- The backend posts a recording to its API, [`summary/api/route/tasks_v2.py`](https://github.com/suitenumerique/meet/blob/main/src/summary/summary/api/route/tasks_v2.py).
- The workers in [`summary/core/celery_worker.py`](https://github.com/suitenumerique/meet/blob/main/src/summary/summary/core/celery_worker.py) transcribe it, summarize it and report back to the backend's `/api/v1.0/recordings/external-process-hook/`.
The queues and the order of the steps are in [How Meet works](../overview/how-meet-works.md#transcription-and-summary), and the settings under [Summary service](../reference/env-variables.md#summary-service).
## Other packages
| Path | What it holds |
|---|---|
| [`src/sdk`](https://github.com/suitenumerique/meet/tree/main/src/sdk) | The SDK in `library/`, published on npm as `@gouvfr-lasuite/visio-sdk`, which adds to another web application a button that creates a Meet link, and a sample application using it in `consumer/`. Its own guide is [`src/sdk/library/CONTRIBUTING.md`](https://github.com/suitenumerique/meet/blob/main/src/sdk/library/CONTRIBUTING.md) |
| [`src/addons/outlook`](https://github.com/suitenumerique/meet/tree/main/src/addons/outlook) | The Outlook add-in that adds a Meet link to an event, calling [`core/addons/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/addons) |
| [`src/mail`](https://github.com/suitenumerique/meet/tree/main/src/mail) | The MJML sources of the emails, compiled as [Email templates](develop.md#email-templates) describes |
## Deployment files
| Path | What it holds |
|---|---|
| [`src/helm/meet`](https://github.com/suitenumerique/meet/tree/main/src/helm/meet) | The Helm chart. Its values are documented in its [`README.md`](https://github.com/suitenumerique/meet/blob/main/src/helm/meet/README.md), which `generate-readme.sh` regenerates from `values.yaml`. [Helm deployment](../self-hosting/kubernetes/helm.md) covers deploying it |
| [`src/helm/helmfile.yaml.gotmpl`](https://github.com/suitenumerique/meet/blob/main/src/helm/helmfile.yaml.gotmpl), [`src/helm/env.d`](https://github.com/suitenumerique/meet/tree/main/src/helm/env.d) | The helmfile and the values of the `dev-keycloak` and `dev-dinum` environments that Tilt deploys |
| [`env.d/development`](https://github.com/suitenumerique/meet/tree/main/env.d/development) | One `.dist` template per service of the development stack, which [First run](develop.md#first-run) copies |
| [`env.d/production.dist`](https://github.com/suitenumerique/meet/tree/main/env.d/production.dist) | The production templates. The directory carries the `.dist` suffix, not the files, so each keeps its name when the [Deployment guide](../self-hosting/compose/deployment-guide.md) downloads it |
| [`Dockerfile`](https://github.com/suitenumerique/meet/blob/main/Dockerfile), [`src/frontend/Dockerfile`](https://github.com/suitenumerique/meet/blob/main/src/frontend/Dockerfile), [`docker/dinum-frontend`](https://github.com/suitenumerique/meet/tree/main/docker/dinum-frontend) | The backend image, the frontend image, and the frontend image with the French government's styles |
| [`deploy/`](https://github.com/suitenumerique/meet/tree/main/deploy), [`Procfile`](https://github.com/suitenumerique/meet/blob/main/Procfile) | The Scalingo deployment, described in [Scalingo](../self-hosting/scalingo.md) |
## The audit log
[Audit logging](../self-hosting/configuration/audit-logging.md) describes what each event holds and how operators collect it.
### Declaring an action
Every action is declared once, in `core/auditing.py`, as an `audit.Action` constant. An action may carry its ECS category and types, which then apply to every event it emits; a type its category does not expect fails at import time:
```python
APPLICATION_TOKEN_ISSUE = audit.Action(
"application.token.issue",
category=EventCategory.AUTHENTICATION,
types=(EventType.START,),
)
ROOM_CREATE = audit.Action("room.create")
```
`core/auditing.py` imports nothing but the audit facility and leaf helpers such as `core.services.transit_code`, so that any module can import it, authentication classes included. Models and authentication classes are registered separately, in `core/audit_registry.py`.
### Auditing a DRF view
A DRF view only declares the actions it audits: everything else is derived from the response.
CRUD actions are mapped in `audit_actions`. An extra action names its own on its route, so that renaming its method cannot silently stop auditing it:
```python
from core import audit, auditing
class RoomViewSet(audit.AuditViewMixin, viewsets.GenericViewSet):
audit_actions = {"create": auditing.ROOM_CREATE, "retrieve": auditing.ROOM_RETRIEVE}
def perform_create(self, serializer):
self.audit_target = serializer.save()
@action(detail=True, methods=["post"], audit_action=auditing.RECORDING_START)
def start_room_recording(self, request, pk=None): ...
```
`AuditViewMixin` fills in the rest:
- The ECS category and types come from the action, or default to `api` and the DRF action.
- The outcome, reason and status code come from the response status: 401, 403 and 429 are `denied`, other errors are `failure`, filed as [Classification](../self-hosting/configuration/audit-logging.md#classification) describes.
- The target is the object `get_object()` returned, unless the view assigns `audit_target`.
- A view can also assign `audit_user_target`, `audit_details` and `audit_actor`, where `None` records no account, or override `get_audit_fields()`.
### Auditing from anywhere else
Outside of `AuditViewMixin`, from a view or deeper in a service, call `audit.log`. A `category` or `types` given here wins over the action's:
```python
audit.log(auditing.USER_PROVISION, target=user)
```
Without `request=`, the event reads the context of the request being served, `audit.request_context()`, which `AuditLogMiddleware` captures when the request comes in. Outside a request, as in a Celery task, the context is empty and the actor is the system.
!!! note
That context holds the Django request. DRF copies the user and auth onto the Django request, but not the authenticator, so a call made inside a DRF view without `request=` should pass `auth_method=`.
### How fields are filled
- **Request fields** are read from the request: the real client address, the path, the user agent and the request id.
- **The actor** comes from `request.user`, `request.auth` and the DRF authenticator, as [Actors](../self-hosting/configuration/audit-logging.md#actors) describes. `audit.register_auth_method` maps the authenticator's class to an auth method, see [Registering models](#registering-models-and-authentication-methods). Without a request, the actor is the system. Override the actor with `actor=`, `actor_type=`, `auth_method=` and `client_id=`; an explicit `actor_type=` keeps the signed-in account. `actor=None` records no account: for a caller failing to authenticate, an application acting before it is given a delegated user, or the system.
- **The target** is described by its model name, its primary key and the `fields` its model is registered with, see [Targets](../self-hosting/configuration/audit-logging.md#targets). A model that is not registered is still identified. The account the action is about, `user.target`, is found from the target, unless given as `user_target=`. Name a service the backend calls with `target_service=`. Any other keyword argument is recorded under `lasuite.details`.
### Emission never raises
A broken configuration or value is reported on the application logger and to Sentry, and the business operation goes on. A registered field that cannot be read is left out of the target, and the event is still emitted.
### Admin pages need nothing
Every admin class, Django's own included, is audited as it is registered, by `AuditedAdminSite` in `core/audit/admin.py`. Registering a new admin's model only adds its category and allowed values.
### Registering models and authentication methods
The project describes itself to the audit facility in code, in `core/audit_registry.py`. Once the audit app is ready, it imports the `audit_registry` module of every installed app.
**`audit.register(Model, ...)`** tells the audit log how to handle a model:
- `fields`: the fields describing it as a target;
- `admin_values`: the fields whose before and after values may be recorded for admin writes;
- `category`: the ECS category of its admin writes;
- `entity_type`: its ECS entity type, when one of the allowed values fits, such as `application` or `user`;
- `user_target`: the attribute holding the account an event on it is about, such as `user` for an access.
A proxy model falls back to its concrete model. Registering a model twice raises `AlreadyRegistered`, and an entity type ECS does not allow raises `ValueError`.
**`audit.register_auth_method(klass, name)`** sets the `lasuite.auth.method` of a DRF authentication class or of a login backend. A DRF class inherits the name of its closest registered base, and DRF's own classes are built in. A login backend must be registered itself, because custom backends often subclass `ModelBackend` just for its permission checks. `ModelBackend` is built in as `password`.
+305
View File
@@ -0,0 +1,305 @@
# Develop locally
The whole stack runs on your machine in Docker Compose, driven by the [`Makefile`](https://github.com/suitenumerique/meet/blob/main/Makefile). The [Code tour](code-tour.md) shows where the code lives, and [Pull requests](https://github.com/suitenumerique/meet/blob/main/CONTRIBUTING.md) how a change gets merged.
## TL;DR
```bash
# 1. Get the code; to propose a change, clone your fork instead, see Pull requests
git clone https://github.com/suitenumerique/meet.git && cd meet
# 2. Build the images, create the database and the demo data, start the stack
make bootstrap FLUSH_ARGS='--no-input'
# 3. Run the frontend with hot reload at localhost:3000, user meet / meet
make frontend-development-install && make run-frontend-development
# 4. Run every test suite, then every linter
make test && make lint && make frontend-lint && make frontend-format
# 5. Stop the stack, keeping its data
make stop
```
## Prerequisites
| Tool | What it is for |
|---|---|
| Git | Cloning the repository and committing |
| Docker Engine with the Compose plugin | Every service of the stack. The commands call `docker compose`, not the old `docker-compose` |
| GNU Make | The `make` targets on this page |
| Node.js 22 and npm | The frontend dev server, linters and tests, which run on your machine. The frontend image builds on [Node 22](https://github.com/suitenumerique/meet/blob/main/src/frontend/Dockerfile) |
| [uv](https://docs.astral.sh/uv/), optional | Adding or upgrading a Python dependency from your machine |
The `Makefile` runs every container under your user ID, through `DOCKER_USER`, so files a container writes into your checkout stay yours. Prefix a hand-typed `docker compose` the same way: `DOCKER_USER=$(id -u):$(id -g) docker compose ...`.
The stack publishes these ports, so they must be free: 3000, 8071, 8080, 8083, 8001, 9000, 1081, 6379, 15432, 5433, 7880, 7881, 7882/UDP, 3478/UDP and 30000 to 30100/UDP. All listen on `127.0.0.1` only, except LiveKit's 7880.
## Start the stack with Docker Compose
### First run
```bash
# Once after cloning, and again to start over
make bootstrap FLUSH_ARGS='--no-input'
```
It empties the database, then creates the Django admin and 100 demo users. It keeps the files you already have in `env.d/development/`, and does not install the frontend's npm dependencies on your machine: `make frontend-development-install` does.
### Where everything answers
| Service | Address | Default login |
|---|---|---|
| Meet | <http://localhost:3000> | `meet` / `meet`, a user of the `meet` realm that Keycloak imports from [`docker/auth/realm.json`](https://github.com/suitenumerique/meet/blob/main/docker/auth/realm.json) |
| Backend API | <http://localhost:8071/api/v1.0/>, schema at <http://localhost:8071/api/v1.0/swagger/> and <http://localhost:8071/api/v1.0/redoc/> | The browser session from signing in to Meet |
| Django admin | <http://localhost:8071/admin/> | `admin@example.com` / `admin`, created by `make superuser` |
| Keycloak | <http://localhost:8083>, behind the `nginx` container | `admin` / `admin` for the administration console |
| LiveKit | `ws://localhost:7880` | API key `devkey`, secret `secret`, from [`docker/livekit/config/livekit-server.yaml`](https://github.com/suitenumerique/meet/blob/main/docker/livekit/config/livekit-server.yaml) |
| Garage, the S3 storage | <http://localhost:9000>, bucket `meet-media-storage`, no web console | Access key `meet-access-key`, secret `meet-secret-access-key` |
| Mailcatcher | <http://localhost:1081>, every email the backend sends | None |
| Summary service API | <http://localhost:8001> | The tenant `api_key` in `env.d/development/summary`, `password` by default |
| PostgreSQL | `localhost:15432`, database `meet` | `dinum` / `pass` |
### Everyday commands
| Command | What it does |
|---|---|
| `make run` | Starts the backend and its services, the summary service and the frontend container. Run it after `make stop`, and after editing `env.d/development/` to recreate the containers reading it |
| `make run-backend` | Starts only what the backend needs: the Django server, its Celery worker, PostgreSQL, Redis, Mailcatcher, Garage, Keycloak behind nginx, and LiveKit with Egress. Use it when the frontend runs outside its container |
| `make run-summary` | Starts the summary service API and its two Celery workers, the transcription one and the summary one |
| `make stop` | Stops every container and keeps them, so the database survives until the next `make run` |
| `make down` | Removes the containers and their network, and the database with the PostgreSQL container: run `make migrate` and `make demo` after the next start. Garage's files stay in `data/media` |
| `make status` | Lists the containers and their state, as `docker compose ps` does |
| `make logs` | Follows the Django server's log. For another service, run `docker compose logs -f <service>`, with a service name from [`compose.yml`](https://github.com/suitenumerique/meet/blob/main/compose.yml) |
| `make demo` | Empties the database, recreates the Django admin and creates the demo users. It asks for confirmation unless you add `FLUSH_ARGS='--no-input'` |
| `make resetdb` | Empties the database and recreates the Django admin, without the demo users |
| `make superuser` | Creates the Django admin `admin@example.com` with password `admin`, or resets that password if the account exists |
| `make help` | Lists the `make` targets with their one-line descriptions. A bare `make` runs it too |
| `make clean` | Runs `git clean -idx`: lists every untracked or ignored file, your env files, `data/` and `node_modules/` included, and asks before deleting them |
### LiveKit agents
`make run` leaves the subtitles agent and the metadata collector off, since each costs CPU and memory. When a feature's agent is stopped, the feature fails silently: the backend still sends the agent work.
| Command | What it does |
|---|---|
| `make run-agent-multi-user-transcriber` | Starts the subtitles agent. Enable it with [`ROOM_SUBTITLE_ENABLED`](../reference/env-variables.md#ROOM_SUBTITLE_ENABLED) in `env.d/development/common`, and give it a speech-to-text provider in `env.d/development/multi_user_transcriber`, see [Subtitles agent](../reference/env-variables.md#subtitles-agent) |
| `make run-agent-metadata-collector` | Starts the metadata collector, which records who speaks when during a transcription. Enable it with [`METADATA_COLLECTOR_ENABLED`](../reference/env-variables.md#METADATA_COLLECTOR_ENABLED) in `env.d/development/common` |
| `make run-agents` | Starts both |
After changing either setting, run `make run-backend` so the backend reads the new value.
### Files in storage
Garage keeps recordings, transcripts and summaries in its own format under `data/media`: read them through these targets.
| Command | What it does |
|---|---|
| `make recordings-list` | Lists the recordings, most recent first, with date, key and size |
| `make recordings-download-latest` | Copies the most recent recording into `data/recordings/` |
| `make transcripts-list`, `make transcripts-download-latest` | The same for transcripts, into `data/transcripts/` |
| `make summaries-list`, `make summaries-download-latest` | The same for summaries, into `data/summaries/` |
## Work on the backend
- The `app-dev` container runs Django's development server with [`src/backend`](https://github.com/suitenumerique/meet/tree/main/src/backend) mounted at `/app`: saving a Python file restarts it.
- The Celery worker, `celery-dev`, does not reload: run `make run-backend` after changing a task.
- The container runs the `Development` configuration, with debug mode and the API schema pages on, `/api/v1.0/swagger/` and `/api/v1.0/redoc/`. Its settings come from `env.d/development/common` and `env.d/development/postgresql`, documented in [Environment variables](../reference/env-variables.md).
| Command | What it does |
|---|---|
| `make makemigrations` | Starts PostgreSQL, then creates a migration in `src/backend/core/migrations/` for every model change. Commit the new file with the change |
| `make migrate` | Starts PostgreSQL, then applies the migrations. Run it after pulling a branch that adds one |
| `make shell` | Opens a Django shell in a new `app-dev` container |
| `make dbshell` | Opens `psql` on the database, inside the running `app-dev` container. The stack must be up |
| `bin/manage <command>` | Runs any `manage.py` command in a new `app-dev` container under `Development`, for example `bin/manage showmigrations` |
| `make back-i18n-generate`, `make back-i18n-compile` | Extract and compile the backend's translatable strings, see [Translations](#translations) |
## Work on the frontend
The `frontend` container on port 3000 serves a production build of [`src/frontend`](https://github.com/suitenumerique/meet/tree/main/src/frontend): it shows a change only after `make build-frontend` and `make run`. The settings it reads at runtime come from the backend, under [Frontend](../reference/env-variables.md#frontend).
For daily work, start the backend with `make run-backend`, then run the Vite dev server on your machine, which reloads on every save:
| Command | What it does |
|---|---|
| `make frontend-development-install` | Runs `npm install` in `src/frontend`. Run it once, and again when `package-lock.json` changes |
| `make run-frontend-development` | Stops the frontend container, then runs `npm run dev`: generates the Panda CSS code and serves the app on <http://localhost:3000> with hot reload, calling the API on <http://localhost:8071>, from [`.env.development`](https://github.com/suitenumerique/meet/blob/main/src/frontend/.env.development) |
| `make build-frontend` | Rebuilds the frontend container's image. Run it before `make run` when you go back to the container |
Every `npm` script runs from `src/frontend`. The `make` targets call the main ones; the others are:
| Command | What it does |
|---|---|
| `npm run build` | Generates the Panda CSS code, type-checks with `tsc`, then builds into `dist/`. Catches the type errors that fail CI's image build |
| `npm run build:debug` | Runs `npm run build` with a bundle size report, written to `rollup-plugin-visualizer/stats.html` |
| `npm run preview` | Serves the last `npm run build` output, to check a production bundle |
| `npm run lint:fix` | Fixes what ESLint can fix by itself |
| `npm run check` | Checks the formatting without changing anything, as CI does: any file Prettier would change fails |
## Tests
| Command | What it does |
|---|---|
| `make test` | Runs the backend suite in parallel, then the summary service and frontend suites, stopping at the first failure. `ARGS` passes pytest arguments to the first two, as in `make test ARGS="-x"` |
| `make test-back` | Runs the backend suite on one process. `make test-back ARGS="core/tests/rooms/"` limits it to a directory |
| `make test-back-parallel` | Runs the backend suite on every CPU core, through pytest-xdist |
| `make test-summary` | Runs the summary service suite |
| `make test-frontend` | Runs `npm test` in `src/frontend`: generates the Panda CSS code, then runs Vitest once. Needs `make frontend-development-install` first |
| `bin/pytest <arguments>` | Runs pytest in a new `app-dev` container, from any directory. Paths are relative to `src/backend` |
| `bin/pytest-summary <arguments>` | Runs pytest in a new summary service container |
Examples of `bin/pytest`:
```bash
# One file
bin/pytest core/tests/rooms/test_api_rooms_list.py
# One test
bin/pytest core/tests/rooms/test_api_rooms_list.py::test_api_rooms_list_authenticated
# Coverage, written as HTML to src/backend/htmlcov/index.html
bin/pytest --cov=core --cov-report=html
```
With `export PATH="$PWD/bin:$PATH"` from the repository root, `pytest` and `manage` run these wrappers directly.
The backend suite needs the `Test` configuration, which `bin/pytest` sets. A bare `docker compose run app-dev pytest` runs under `Development`, where the external API and add-ons tests fail.
**Backend tests** live in [`src/backend/core/tests/`](https://github.com/suitenumerique/meet/tree/main/src/backend/core/tests):
- Model tests as `test_models_<area>.py`, API tests as `test_api_<area>_*.py`, in a subdirectory such as `rooms/` or `recording/` where an area has many.
- Plain pytest functions, marked `pytest.mark.django_db` when they touch the database, calling the API through DRF's `APIClient`.
- Data comes from the factories in [`core/factories.py`](https://github.com/suitenumerique/meet/blob/main/src/backend/core/factories.py).
- They use the real test database, and patch only what leaves the backend, such as `core.utils.create_livekit_client` for LiveKit or the S3 client.
**Frontend tests** sit next to the code they test, as `*.test.ts` files.
The agents have no test suite. The SDK has none either, and CI builds it instead, see [Lint and format](#lint-and-format).
## Lint and format
The `make` targets fix what they can in place. CI only checks, so run them before pushing and commit what they change.
| Command | What it does |
|---|---|
| `make lint` | Runs `make lint-back`, `make lint-agents` and `make lint-summary` |
| `make lint-back` | Runs `ruff format`, `ruff check --fix`, then `pylint` on the `meet`, `demo` and `core` packages, in a backend container started without its services |
| `make lint-agents`, `make lint-summary` | Runs `ruff format` and `ruff check --fix` on the agents or on the summary service |
| `make lint-ruff-format`, `make lint-ruff-check`, `make lint-pylint` | Runs one backend step alone. `make lint-pylint` checks all of `meet`, `demo` and `core`, despite its help text saying only files changed from `main` |
| `make frontend-lint` | Runs ESLint on the frontend, where any warning fails |
| `make frontend-format` | Runs Prettier on `src/frontend/src`, rewriting the files |
| `cd src/sdk/library && npm ci && npm run lint && npm run check && npm run build` | Lints, checks the formatting of, and builds the SDK, as CI does. Run it when you touch [`src/sdk`](https://github.com/suitenumerique/meet/tree/main/src/sdk) |
CI also checks commit messages, spelling and shell scripts: [What CI checks](https://github.com/suitenumerique/meet/blob/main/CONTRIBUTING.md#what-ci-checks) gives the local command for each.
## Translations
The interface ships in English, French, German, Dutch and Spanish, and every string is translated in the pull request that adds it.
**Frontend.** A component reads its strings through `t()` from `react-i18next`, by key, from a namespace file in [`src/frontend/src/locales/<language>/`](https://github.com/suitenumerique/meet/tree/main/src/frontend/src/locales). [`HandToggle.tsx`](https://github.com/suitenumerique/meet/blob/main/src/frontend/src/features/rooms/livekit/components/controls/HandToggle.tsx) reads `controls.hand.raise` or `controls.hand.lower` from `rooms.json`:
```tsx
const { t } = useTranslation('rooms', { keyPrefix: 'controls.hand' })
// ...
const tooltipLabel = isHandRaised ? 'lower' : 'raise'
// ...
aria-label={t(tooltipLabel)} // controls.hand.raise or controls.hand.lower
```
| Command | What it does |
|---|---|
| `make frontend-i18n-extract` | Runs `npm run i18n:extract`: adds each new `t()` key, empty, in all five languages, removes unused keys and sorts the files. Fill every empty value before pushing: it shows as blank text, not a fallback |
**Backend.** Emails and API messages use Django's gettext, with one catalog per language in [`src/backend/locale/`](https://github.com/suitenumerique/meet/tree/main/src/backend/locale).
| Command | What it does |
|---|---|
| `make back-i18n-generate` | Runs `makemessages` for every language, which adds new strings to each `django.po` file. Translate them there |
| `make back-i18n-compile` | Compiles the `.po` files into the `.mo` files Django reads. `make bootstrap` runs it; run it again to see your translations |
The `crowdin-*`, `i18n-generate-and-upload` and `i18n-download-and-compile` targets sync the catalogs with Crowdin. They are for maintainers, and need a Crowdin token in `env.d/development/crowdin`.
## Email templates
The emails are written in MJML in [`src/mail/mjml/`](https://github.com/suitenumerique/meet/tree/main/src/mail/mjml) and compiled into the templates the backend sends.
| Command | What it does |
|---|---|
| `make mails-install` | Installs the generator's npm dependencies, in a Node container. `make bootstrap` runs it |
| `make mails-build` | Compiles every `.mjml` file into HTML and plain text under `src/backend/core/templates/mail/`. Run it after editing a template; Mailcatcher shows the result |
## Add a dependency
Every dependency is pinned to an exact version. CI installs from the lock files, with `uv sync --locked` and `npm ci`, so a manifest edited without its lock file fails.
| Command | What it does |
|---|---|
| `cd src/backend && uv add "<package>==<version>"` | Adds a backend dependency to `pyproject.toml` and `uv.lock`. Add `--dev` for a tool only tests or linters use |
| `make build-backend` | Rebuilds the backend image with the new dependency. `uv` exists only during the build, so it cannot install into a running container |
| `DOCKER_USER=$(id -u):$(id -g) docker compose up -d --force-recreate --renew-anon-volumes app-dev celery-dev` | Restarts the backend on the new image. `--renew-anon-volumes` replaces the old container's virtual environment volume, which a plain restart keeps |
| `cd src/agents && uv add "<package>==<version>"`, then `make build-agents` | The same for the agents. `make build-agents` rebuilds the subtitles agent; rebuild the metadata collector with `docker compose build metadata-collector-dev` |
| `cd src/summary && uv add "<package>==<version>"`, then `docker compose build app-summary-dev celery-summary-transcribe celery-summary-summarize` | The same for the summary service, whose three containers each build their own image |
| `cd src/frontend && npm install --save-exact <package>@<version>` | Adds a frontend dependency to `package.json` and `package-lock.json`. Run `make build-frontend` if you use the frontend container |
## Nix with devenv
On a Nix workstation, [`devenv.nix`](https://github.com/suitenumerique/meet/blob/main/devenv.nix) provides the tools of [Prerequisites](#prerequisites) instead:
| Command | What it does |
|---|---|
| `devenv shell` | Opens a shell with Python 3.13, Node.js 22, uv, gettext, the PostgreSQL client, the Docker and Podman clients, and installs gitlint as a commit-message hook. It points `docker` at the Podman socket: set `MEET_PODMAN_SOCKET=0` before entering to keep Docker |
| `devenv --profile agents shell` | Adds what the LiveKit agents need, including the LiveKit CLI. The `summary` profile adds Redis, and `k8s` adds the tools listed under [Kubernetes with Tilt](#kubernetes-with-tilt) |
| `meet-venv` | Inside the shell, creates or refreshes the virtual environments of `src/backend`, `src/agents` and `src/summary` |
## Kubernetes with Tilt
[Tilt](https://tilt.dev/) runs Meet in a local Kubernetes cluster with the [Helm chart](https://github.com/suitenumerique/meet/tree/main/src/helm) and copies your edits into the running pods. Use it only when a change touches the chart or depends on Kubernetes.
Besides Docker, it needs:
| Tool | What it is for |
|---|---|
| [kind](https://kind.sigs.k8s.io/) | The local cluster |
| [kubectl](https://kubernetes.io/docs/tasks/tools/) | Talking to the cluster |
| [Helm](https://helm.sh/) and [helmfile](https://helmfile.readthedocs.io/) | Rendering the chart and its development services from [`src/helm/helmfile.yaml.gotmpl`](https://github.com/suitenumerique/meet/blob/main/src/helm/helmfile.yaml.gotmpl) |
| [Tilt](https://docs.tilt.dev/install.html) | Building the images, deploying them and syncing your edits |
| [mkcert](https://github.com/FiloSottile/mkcert) | The local certificate authority behind the cluster's HTTPS |
| Command | What it does |
|---|---|
| [`./bin/start-kind.sh`](https://github.com/suitenumerique/meet/blob/main/bin/start-kind.sh) | Run it once. It creates a kind cluster `suite` serving `*.127.0.0.1.nip.io` over HTTPS, with a mkcert certificate authority and an image registry on `localhost:5001`. It pipes [`create_cluster.sh`](https://github.com/numerique-gouv/tools/blob/main/kind/create_cluster.sh) from `numerique-gouv/tools` to `bash`: read that script first |
| `make build-k8s-cluster` | Copies `env.d/development/kube-secret.dist` if needed. It does not create the cluster |
| `make start-tilt-keycloak` | Runs `tilt up` with [`bin/Tiltfile`](https://github.com/suitenumerique/meet/blob/main/bin/Tiltfile) in the `meet` namespace, with a Keycloak in the cluster. Builds the backend, frontend, summary, agents and LiveKit images, deploys the chart, applies the migrations and creates the Django admin once |
| `make start-tilt-dinum` | The same, with the DINUM-styled frontend from [`docker/dinum-frontend`](https://github.com/suitenumerique/meet/tree/main/docker/dinum-frontend) |
| `tilt down --namespace=meet -f ./bin/Tiltfile` | Deletes what Tilt deployed. Stopping `tilt up` with Ctrl+C leaves the deployment running |
| `kind delete cluster --name suite` | Deletes the cluster |
Tilt's dashboard is at <http://localhost:10350/> and Meet at <https://meet.127.0.0.1.nip.io/>. On the `meet-backend` resource, the **Run makemigration** and **Run database migration** buttons run those commands in the backend pod.
## Work on this documentation site
[Zensical](https://zensical.org/) builds this site from the Markdown in [`docs/`](https://github.com/suitenumerique/meet/tree/main/docs), with its name and navigation in [`zensical.toml`](https://github.com/suitenumerique/meet/blob/main/zensical.toml). It needs only Docker; run each command from the repository root.
| Command | What it does |
|---|---|
| `docker run --rm -it -p 8000:8000 -v "$PWD":/docs zensical/zensical` | Serves the site on <http://localhost:8000> and rebuilds a page when you save its file |
| `docker run --rm -v "$PWD":/docs zensical/zensical build` | Builds the static site into `site/`, which Git ignores |
| `docker pull zensical/zensical` | Updates the Zensical image |
The home page is `docs/index.md`. Do not add a `docs/README.md`: Zensical would build it into the same `index.html`.
A page follows these rules:
- **One fact lives in one place.** Every other page links to it rather than repeating it.
- **Environment variables are documented only in [Environment variables](../reference/env-variables.md).** Another page names the variable and links its row.
- **Problems and their fixes go only in [Troubleshooting](../reference/troubleshooting.md).**
- **Source files are linked on GitHub, not described line by line.** Link `https://github.com/suitenumerique/meet/blob/main/<path>`: a relative link to a file outside `docs/` works in the editor but is dead on the built site.
- **Every screenshot is a figure with a caption:**
```html
<figure markdown="span">
![Participants panel](../assets/participants-panel.png)
<figcaption>Participants panel, a menu per name</figcaption>
</figure>
```
Two screenshots side by side go in one `<div class="figure-row" markdown>`. Images live in [`docs/assets/`](https://github.com/suitenumerique/meet/tree/main/docs/assets).
- **An icon inside a sentence or a table has `class="off-glb"`**, which keeps it out of the lightbox that opens screenshots full size: `<img class="off-glb" src="../assets/icons/mic-line.svg" width="20" />`.
- **A new page is added to `nav` in `zensical.toml`**, or it builds without appearing in the navigation.
CI's spelling and shellcheck jobs cover `docs/` too, see [What CI checks](https://github.com/suitenumerique/meet/blob/main/CONTRIBUTING.md#what-ci-checks).
-145
View File
@@ -1,145 +0,0 @@
# Getting Started
Before setting up, let's review Visio's architecture.
Visio consists of four main components that run simultaneously:
- React frontend, built with Vite.js
- Django server
- LiveKit server
- FastAPI server (optional, required for AI beta features)
These components rely on a few key services:
- PostgreSQL for storing data (users, rooms, recordings)
- Redis for caching and inter-service communication
- Garage for storing files (room recordings)
- Celery workers for meeting transcript (optional, required for AI beta features)
We provide two stack options for getting Visio up and running for development:
- Docker Compose stack (recommended for most users)
- Kubernetes stack powered by Tilt (Advanced)
We recommend starting with the **Docker Compose** option for simplicity. However, if you're comfortable with running Kubernetes locally, the advanced option mirrors the production environment and provides most of the tools required for development (e.g., hot reloading).
These instructions are for macOS or Ubuntu. For other distros, adjust as needed.
If any steps are outdated, please let us know!
---
We also provide **GNU make utilities**. To view all available Make rules, run:
```shellscript
$ make help
```
---
## Need Help?
If you need any assistance or have questions while getting started, feel free to reach out to @lebaudantoine anytime! Antoine is available to help you onboard and guide you through the process. Chat with him @antoine.lebaud:matrix.org, or from the [support hotline](https://go.crisp.chat/chat/embed/?website_id=58ea6697-8eba-4492-bc59-ad6562585041).
---
## Option 1: Developing with Docker
### Prerequisites
1. Ensure you have a recent version of **Docker** and **Docker Compose** installed:
```shellscript
$ docker -v
Docker version 20.10.2, build 2291f61
$ docker compose version
Docker Compose version v2.32.4
```
2. Install **LiveKit CLI** by following the instructions available in the [official repository](https://github.com/livekit/livekit-cli). After installation, verify that it's working:
```shellscript
$ lk --version
lk version 2.3.1
```
---
### Project Bootstrap
1. Bootstrap the project using the **Make** command. This will build the `app` container, install dependencies, run database migrations, and compile translations:
```shellscript
$ make bootstrap FLUSH_ARGS='--no-input'
```
2. Access the project:
- The frontend is available at [http://localhost:3000](http://localhost:3000) with the default credentials:
- username: meet
- password: meet
- The Django backend is available at [http://localhost:8071](http://localhost:8071)
---
## Developing
- To **stop** the application:
```shellscript
$ make stop
```
- To **restart** the application:
```shellscript
$ make run
```
- For **frontend development**, start all backend services without the frontend container:
```shellscript
$ make run-backend
```
Then:
```shellscript
$ make frontend-development-install
$ make run-frontend-development
```
Which is equivalent to these direct npm commands:
```shellscript
$ cd src/frontend
$ npm i
$ npm run dev
```
---
## Adding Content
You can bootstrap demo data with a single command:
```shellscript
$ make demo
```
---
## Option 2: Developing with Kubernetes
Visio is deployed across staging, preprod, and production environments using **Kubernetes (K8s)**. Reproducing the environment locally is crucial for developing new features or debugging.
This is facilitated by [Tilt](https://tilt.dev/), which provides Kubernetes-like development for local environments, enabling smart rebuilds and live updates.
### Getting Started
Make sure you have the following installed:
- kubectl
- helm
- helmfile
- tilt
To build and start the Kubernetes cluster using **Kind**:
```shellscript
$ make build-k8s-cluster
```
Once the Kubernetes cluster is ready, start the application stack locally:
```shellscript
$ make start-tilt-keycloak
```
Monitor Tilt’s progress at [http://localhost:10350/](http://localhost:10350/). After Tilt actions finish, you can access the app at [https://meet.127.0.0.1.nip.io/](https://meet.127.0.0.1.nip.io/).
-89
View File
@@ -1,89 +0,0 @@
services:
postgresql:
image: postgres:16
healthcheck:
test: ["CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}"]
interval: 1s
timeout: 2s
retries: 300
env_file:
- env.d/postgresql
- env.d/common
volumes:
- ./data/databases/backend:/var/lib/postgresql/data
redis:
image: redis:5
backend:
image: lasuite/meet-backend:latest
user: ${DOCKER_USER:-1000}
restart: always
env_file:
- .env
- env.d/common
- env.d/postgresql
healthcheck:
test: ["CMD", "python", "manage.py", "check"]
interval: 15s
timeout: 30s
retries: 20
start_period: 10s
depends_on:
postgresql:
condition: service_healthy
restart: true
redis:
condition: service_started
livekit:
condition: service_started
frontend:
image: lasuite/meet-frontend:latest
user: "${DOCKER_USER:-1000}"
entrypoint:
- /docker-entrypoint.sh
command: ["nginx", "-g", "daemon off;"]
env_file:
- .env
- env.d/common
# Uncomment and set your values if using our nginx proxy example
# environment:
# - VIRTUAL_HOST=${MEET_HOST} # used by nginx proxy
# - VIRTUAL_PORT=8083 # used by nginx proxy
# - LETSENCRYPT_HOST=${MEET_HOST} # used by lets encrypt to generate TLS certificate
depends_on:
backend:
condition: service_healthy
volumes:
- ./default.conf.template:/etc/nginx/templates/docs.conf.template
# Uncomment if using our nginx proxy example
# networks:
# - proxy-tier
# - default
livekit:
image: livekit/livekit-server:latest
command: --config /config.yaml
ports:
- 7881:7881/tcp
- 7882:7882/udp
volumes:
- ./livekit-server.yaml:/config.yaml
# Uncomment and set your values if using our nginx proxy example
# environment:
# - VIRTUAL_HOST=${LIVEKIT_HOST} # used by nginx proxy
# - VIRTUAL_PORT=7880 # used by nginx proxy
# - LETSENCRYPT_HOST=${LIVEKIT_HOST} # used by lets encrypt to generate TLS certificate
depends_on:
redis:
condition: service_started
# Uncomment if using our nginx proxy example
# networks:
# - proxy-tier
# - default
# Uncomment if using our nginx proxy example
#networks:
# proxy-tier:
# external: true
-91
View File
@@ -1,91 +0,0 @@
# Deploy and Configure Keycloak for Meet
## Installation
> [!CAUTION]
> We provide those instructions as an example, for production environments, you should follow the [official documentation](https://www.keycloak.org/documentation).
### Step 1: Prepare your working environment:
```bash
mkdir -p keycloak/env.d && cd keycloak
curl -o compose.yaml https://raw.githubusercontent.com/suitenumerique/meet/refs/heads/main/docs/examples/compose/keycloak/compose.yaml
curl -o env.d/kc_postgresql https://raw.githubusercontent.com/suitenumerique/meet/refs/heads/main/env.d/production.dist/kc_postgresql
curl -o env.d/keycloak https://raw.githubusercontent.com/suitenumerique/meet/refs/heads/main/env.d/production.dist/keycloak
```
### Step 2:. Update `env.d/` files
The following variables need to be updated with your own values, others can be left as is:
```env
POSTGRES_PASSWORD=<generate postgres password>
KC_HOSTNAME=https://id.yourdomain.tld # Change with your own URL
KC_BOOTSTRAP_ADMIN_PASSWORD=<generate your password>
```
### Step 3: Expose keycloak instance on https
> [!NOTE]
> You can skip this section if you already have your own setup.
To access your Keycloak instance on the public network, it needs to be exposed on a domain with SSL termination. You can use our [example with nginx proxy and Let's Encrypt companion](../nginx-proxy/README.md) for automated creation/renewal of certificates using [acme.sh](http://acme.sh).
If following our example, uncomment the environment and network sections in compose file and update it with your values.
```yaml
version: '3'
services:
keycloak:
...
# Uncomment and set your values if using our nginx proxy example
# environment:
# - VIRTUAL_HOST=id.yourdomain.tld # used by nginx proxy
# - VIRTUAL_PORT=8080 # used by nginx proxy
# - LETSENCRYPT_HOST=id.yourdomain.tld # used by lets encrypt to generate TLS certificate
...
# Uncomment if using our nginx proxy example
# networks:
# - proxy-tier
# - default
# Uncomment if using our nginx proxy example
#networks:
# proxy-tier:
# external: true
```
### Step 4: Start the service
```bash
`docker compose up -d`
```
Your keycloak instance is now available on https://id.yourdomain.tld
> [!CAUTION]
> Version of the images are set to latest, you should pin it to the desired version to avoid unwanted upgrades when pulling latest image. You can find available versions on [Keycloak registry](https://quay.io/repository/keycloak/keycloak?tab=tags).
## Creating an OIDC Client for Meet Application
### Step 1: Create a New Realm
1. Log in to the Keycloak administration console.
2. Navigate to the realm tab and click on the "Create realm" button.
3. Enter the name of the realm - `meet`.
4. Click "Create".
### Step 2: Create a New Client
1. Navigate to the "Clients" tab.
2. Click on the "Create client" button.
3. Enter the client ID - e.g. `meet`.
4. Enable "Client authentication" option.
6. Set the "Valid redirect URIs" to the URL of your meet application suffixed with `/*` - e.g., "https://meet.example.com/*".
1. Set the "Web Origins" to the URL of your meet application - e.g. `https://meet.example.com`.
1. Click "Save".
### Step 3: Get Client Credentials
1. Go to the "Credentials" tab.
2. Copy the client ID (`meet` in this example) and the client secret.
@@ -1,36 +0,0 @@
services:
postgresql:
image: postgres:16
healthcheck:
test: ["CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}"]
interval: 1s
timeout: 2s
retries: 300
env_file:
- env.d/kc_postgresql
volumes:
- ./data/keycloak:/var/lib/postgresql/data/pgdata
keycloak:
image: quay.io/keycloak/keycloak:latest
command: ["start"]
env_file:
- env.d/kc_postgresql
- env.d/keycloak
# Uncomment and set your values if using our nginx proxy example
# environment:
# - VIRTUAL_HOST=id.yourdomain.tld # used by nginx proxy
# - VIRTUAL_PORT=8080 # used by nginx proxy
# - LETSENCRYPT_HOST=id.yourdomain.tld # used by lets encrypt to generate TLS certificate
depends_on:
postgresql:
condition: service_healthy
restart: true
# Uncomment if using our nginx proxy example
# networks:
# - proxy-tier
# - default
#
#networks:
# proxy-tier:
# external: true
@@ -1,39 +0,0 @@
# Nginx proxy with automatic SSL certificates
> [!CAUTION]
> We provide those instructions as an example, for extended development or production environments, you should follow the [official documentation](https://github.com/nginx-proxy/acme-companion/tree/main/docs).
Nginx-proxy sets up a container running nginx and docker-gen. docker-gen generates reverse proxy configs for nginx and reloads nginx when containers are started and stopped.
Acme-companion is a lightweight companion container for nginx-proxy. It handles the automated creation, renewal and use of SSL certificates for proxied Docker containers through the ACME protocol.
## Installation
### Step 1: Prepare your working environment:
```bash
mkdir nginx-proxy && cd nginx-proxy
curl -o compose.yaml https://raw.githubusercontent.com/suitenumerique/meet/refs/heads/main/docs/examples/compose/nginx-proxy/compose.yaml
```
### Step 2: Edit `DEFAULT_EMAIL` in the compose file.
Albeit optional, it is recommended to provide a valid default email address through the `DEFAULT_EMAIL` environment variable, so that Let's Encrypt can warn you about expiring certificates and allow you to recover your account.
### Step 3: Create docker network
Containers need share the same network for auto-discovery.
```bash
docker network create proxy-tier
```
### Step 4: Start service
```bash
docker compose up -d
```
## Usage
Once both nginx-proxy and acme-companion containers are up and running, start any container you want proxied with environment variables `VIRTUAL_HOST` and `LETSENCRYPT_HOST` both set to the domain(s) your proxied container is going to use.
@@ -1,36 +0,0 @@
services:
nginx-proxy:
image: nginxproxy/nginx-proxy
container_name: nginx-proxy
ports:
- "80:80"
- "443:443"
volumes:
- html:/usr/share/nginx/html
- certs:/etc/nginx/certs:ro
- /var/run/docker.sock:/tmp/docker.sock:ro
networks:
- proxy-tier
acme-companion:
image: nginxproxy/acme-companion
container_name: nginx-proxy-acme
environment:
- DEFAULT_EMAIL=mail@yourdomain.tld
volumes_from:
- nginx-proxy
volumes:
- certs:/etc/nginx/certs:rw
- acme:/etc/acme.sh
- /var/run/docker.sock:/var/run/docker.sock:ro
networks:
- proxy-tier
networks:
proxy-tier:
external: true
volumes:
html:
certs:
acme:

Some files were not shown because too many files have changed in this diff Show More