studio/meet
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
0fe8d9b6811e9a4ef553031ad68603cce9840ad2
meet/src/helm/env.d/dev/values.meet.yaml.gotmpl

286 lines
8.8 KiB
Go Template
Raw Normal View History

🔧(helm) offer a standalone dev environment Offer a standalone dev environment or a dinum specific dev environment with ProConnect authentication. Needed to refactor the way secrets are managed in the project, and also re-organize the Helm chart to make it totally standalone. Particulary useful for external wanting to run the project. Work done by @rouja.
2024-12-20 14:07:01 +01:00
secrets:
- name: oidcLogin
itemId: a25effec-eaea-4ce1-9ed8-3a3cc1c734db
field: username
podVariable: OIDC_RP_CLIENT_ID
♻️(helm) refactor clusterSecretStore and ExternalSecret deployments Refactored ClusterSecretStore and ExternalSecret deployment to support VaultWarden custom fields beyond login/password, including multi-line values via file input. Also made the secret template name configurable for added flexibility. ClusterSecretStore are supposed to be cluster-wide objects, it's useless to precise any namespace.
2025-01-13 12:20:35 +01:00
clusterSecretStore: bitwarden-login-meet
🔧(helm) offer a standalone dev environment Offer a standalone dev environment or a dinum specific dev environment with ProConnect authentication. Needed to refactor the way secrets are managed in the project, and also re-organize the Helm chart to make it totally standalone. Particulary useful for external wanting to run the project. Work done by @rouja.
2024-12-20 14:07:01 +01:00
- name: oidcPass
itemId: a25effec-eaea-4ce1-9ed8-3a3cc1c734db
field: password
podVariable: OIDC_RP_CLIENT_SECRET
♻️(helm) refactor clusterSecretStore and ExternalSecret deployments Refactored ClusterSecretStore and ExternalSecret deployment to support VaultWarden custom fields beyond login/password, including multi-line values via file input. Also made the secret template name configurable for added flexibility. ClusterSecretStore are supposed to be cluster-wide objects, it's useless to precise any namespace.
2025-01-13 12:20:35 +01:00
clusterSecretStore: bitwarden-login-meet
🔐(helm) configure Brevo marketing tool Using VaultWarden, added a dev Brevo API key. In the "dev" stack, enable Brevo to validate new users are signed-up to the marketing emails.
2025-01-13 21:21:16 +01:00
- name: brevoApiKey
itemId: 99107889-6124-4436-97cc-a5193f28443f
field: password
podVariable: BREVO_API_KEY
clusterSecretStore: bitwarden-login-meet
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
image:
🚚(DockerHub) rename DockerHub images I have created two new repositories on DockerHub, one for the currently existing backend image, and one for the future frontend image. I searched-replaced all occurences of "lasuite/impress-frontend" or "lasuite/impress-backend". One image won't exist anymore, "impress-y-webrtc-signaling", I have removed the steps building and pushing its image to the DockerHub account.
2024-07-01 18:32:29 +02:00
repository: localhost:5001/meet-backend
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
pullPolicy: Always
tag: "latest"
backend:
replicas: 1
envVars:
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
DJANGO_CSRF_TRUSTED_ORIGINS: https://meet.127.0.0.1.nip.io,http://meet.127.0.0.1.nip.io
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
DJANGO_CONFIGURATION: Production
🔒️(helm) allow server host and whitelist pod IP for health checks Updated Django's ALLOWED_HOSTS setting from '*' to the specific host of the server. Setting ALLOWED_HOSTS to '*' is a security risk as it allows any host to access the application, potentially exposing it to malicious attacks. Restricting ALLOWED_HOSTS to the server's host ensures only legitimate requests are processed. In a Kubernetes environment, we also needed to whitelist the pod's IP address to allow health checks to pass. This ensures that Kubernetes liveness and readiness probes can access the application to verify its health.
2024-08-05 16:58:11 +02:00
DJANGO_ALLOWED_HOSTS: meet.127.0.0.1.nip.io
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
DJANGO_SECRET_KEY: {{ .Values.djangoSecretKey }}
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
DJANGO_SETTINGS_MODULE: meet.settings
🔇(backend) silence security warnings for reverse proxy setup Silenced certain Django security warnings because the application is served behind a reverse proxy. These warnings are not applicable in our deployment context, where the reverse proxy handles these security concerns. This change ensures relevant security measures are appropriately managed while avoiding unnecessary warnings. Any question? asked @rouja. /!\ actually, this commit is not working, and should be fixed.
2024-08-02 21:14:21 +02:00
DJANGO_SILENCED_SYSTEM_CHECKS: security.W004, security.W008
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
DJANGO_SUPERUSER_PASSWORD: admin
DJANGO_EMAIL_HOST: "mailcatcher"
DJANGO_EMAIL_PORT: 1025
DJANGO_EMAIL_USE_SSL: False
✨(backend) add email notifications for screen recordings Implement backend method to send email notifications when screen recordings are ready for download. Enables users to be alerted when their recordings are available. Frontend implementation to follow in upcoming commits. This service is triggered by the storage hook from Minio. Add minimal unit test coverage for notification service, addressing previous lack of tests in this area. The notification service was responsible for calling the unstable summary service feature, which was developped way too quickly. The email template has been reviewed by a LLM, to make it user-friendly and crystal clear.
2025-04-14 18:48:50 +02:00
DJANGO_EMAIL_BRAND_NAME: "La Suite Numérique"
DJANGO_EMAIL_SUPPORT_EMAIL: "test@yopmail.com"
DJANGO_EMAIL_LOGO_IMG: https://meet.127.0.0.1.nip.io/assets/logo-suite-numerique.png
🩹(backend) fix email domain environment variable Value wasn't properly set to a domain, but to an URL. Fix it.
2025-04-15 15:54:49 +02:00
DJANGO_EMAIL_DOMAIN: meet.127.0.0.1.nip.io
✨(backend) introduce configuration for app base URL Add new application base URL configuration setting. While somewhat redundant with existing domain setting, these serve different purposes in the application. Base URL will be used for constructing complete URLs in notifications and external references.
2025-04-15 15:55:56 +02:00
DJANGO_EMAIL_APP_BASE_URL: https://meet.127.0.0.1.nip.io
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
OIDC_OP_JWKS_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/jwks
OIDC_OP_AUTHORIZATION_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/authorize
OIDC_OP_TOKEN_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/token
OIDC_OP_USER_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/userinfo
OIDC_OP_LOGOUT_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/session/end
🔧(helm) offer a standalone dev environment Offer a standalone dev environment or a dinum specific dev environment with ProConnect authentication. Needed to refactor the way secrets are managed in the project, and also re-organize the Helm chart to make it totally standalone. Particulary useful for external wanting to run the project. Work done by @rouja.
2024-12-20 14:07:01 +01:00
OIDC_RP_CLIENT_ID:
secretKeyRef:
name: backend
key: OIDC_RP_CLIENT_ID
OIDC_RP_CLIENT_SECRET:
secretKeyRef:
name: backend
key: OIDC_RP_CLIENT_SECRET
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
OIDC_RP_SIGN_ALGO: RS256
🛂(backend) request given and usual name scopes from ProConnect Request the necessary scopes from ProConnect service. Update configurations in every environments. Note: ask given_name and usual_name scopes to get users' info. (these scopes should be granted by default by ProConnect when requesting a client id client secret)
2024-11-15 23:30:30 +01:00
OIDC_RP_SCOPES: "openid email given_name usual_name"
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
OIDC_REDIRECT_ALLOWED_HOSTS: https://meet.127.0.0.1.nip.io
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
OIDC_AUTH_REQUEST_EXTRA_PARAMS: "{'acr_values': 'eidas1'}"
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
LOGIN_REDIRECT_URL: https://meet.127.0.0.1.nip.io
LOGIN_REDIRECT_URL_FAILURE: https://meet.127.0.0.1.nip.io
LOGOUT_REDIRECT_URL: https://meet.127.0.0.1.nip.io
♻️(tilt) remove bitnami dependencies from dev stack Remove dependencies on bitnami Helm charts since recent changes in bitnami organization led to charts no longer being maintained or published. Enhanced the Tilt dependencies to avoid any bootstrap or refresh errors while developping using the Tilt stack. Making components dependant from each others increase slightly the time required to spin up the stack the first time.
2025-08-01 18:04:56 +02:00
DB_HOST: postgres
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
DB_NAME: meet
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
DB_USER: dinum
DB_PASSWORD: pass
DB_PORT: 5432
REDIS_URL: redis://default:pass@redis-master:6379/1
STORAGES_STATICFILES_BACKEND: django.contrib.staticfiles.storage.StaticFilesStorage
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
{{- with .Values.livekit.keys }}
{{- range $key, $value := . }}
LIVEKIT_API_SECRET: {{ $value }}
LIVEKIT_API_KEY: {{ $key }}
{{- end }}
{{- end }}
🔧(frontend) pass dynamically the LiveKit url It seems appropriate that backend owns the responsability of knowing any information/configurations of the LiveKit server. Then, it shares those with the frontend. Please see my previous commit to understand why environment variables are not appropriate for deployment in several remove environments. As of today, the LiveKit server URL is the only configuration exposed dynamically to the frontend. Thus, it doesn't justify adding a new route to the API, responsible for exposing configurations (e.g. /configuration). As the frontend needs to call the backend when it wants to initiate a new webconference room, let's pass the server URL when retrieving the room's token. It is relevant, to get both the room location and the keys to open the room in the same call. I prefered to be pragmatic, if the need appears any soon, I would refactor these parts.
2024-07-10 21:16:07 +02:00
LIVEKIT_API_URL: https://livekit.127.0.0.1.nip.io/
🐛(backend) fix ignore recording webhook events Fix an unexpected behavior where filtering LiveKit webhook events sometimes failed because the room name was not reliably extracted from the webhook data, causing notifications to be ignored. Configure the same filtering logic locally to avoid missing this kind of issue in the future.
2026-01-05 13:31:15 +01:00
LIVEKIT_WEBHOOK_EVENTS_FILTER_REGEX: "[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}"
🛂(backend) disallow unregistered rooms Require users to create a room in the database before requesting a LiveKit token. If user request an access token for a room that doesn't exist in our db, its request would end in a 404 error. Ensure that rooms must be registered by a user before they can be accessed. By default, all created rooms remain public, allowing anonymous users to join any room created by a logged-in user. However, anonymous users cannot create rooms themselves.
2024-07-26 00:41:17 +02:00
ALLOW_UNREGISTERED_ROOMS: False
🔧(helm) configure support and analytics Declare the expected support and analytics env variables expected by the frontend for each environment. To avoid consuming too much credits from our PostHog free tier plan.
2024-09-24 23:20:48 +02:00
FRONTEND_SILENCE_LIVEKIT_DEBUG: False
FRONTEND_SUPPORT: "{'id': '58ea6697-8eba-4492-bc59-ad6562585041'}"
✨(backend) add S3 objects Inspired by Impress and @sampaccoud's work. We use Indie Hoster’s Kubernetes objects in staging and production. In the "dev" environment, we install the `bitnami/minio` chart to mimic Indie Hoster’s MinIO setup. To access the MinIO admin interface in dev, use port forwarding; the interface runs on port 9001.
2024-10-25 12:22:41 +02:00
AWS_S3_ENDPOINT_URL: http://minio.meet.svc.cluster.local:9000
AWS_S3_ACCESS_KEY_ID: meet
AWS_S3_SECRET_ACCESS_KEY: password
AWS_STORAGE_BUCKET_NAME: meet-media-storage
🔧(backend) enable recording and storage hook Update values for dev and staging environment to enable recording-related endpoints. A new secret need to be created. Production values will be added in an upcoming commit.
2024-11-26 23:40:03 +01:00
AWS_S3_REGION_NAME: local
RECORDING_ENABLE: True
RECORDING_STORAGE_EVENT_ENABLE: True
RECORDING_STORAGE_EVENT_TOKEN: password
💩(backend) notify the summary service when a new recording is available Draft a piece of code to try the feature in staging. I'll consolidate this implementation ASAP, as soon we have a first implementation functional. What's missing? - when owners are multiple - retry when the backend cannot reach the summary service - factorize the key oneliner, duplicated from the egress service - optimize SQL query - unit tests
2024-12-02 13:16:43 +01:00
SUMMARY_SERVICE_ENDPOINT: http://meet-summary:80/api/v1/tasks/
SUMMARY_SERVICE_API_TOKEN: password
✨(summary) link transcript to their downloadable recording Link the transcription document to its related recording by adding a short header explaining that users can download the audio file via a dedicated link. This was a highly requested feature, as many users need to keep their audio files. As part of a small refactor, remove the argument length check in the metadata analytics class. The hardcoded argument count made code evolution harder and was easy to forget updating. Argument unwrapping remains fragile and should be redesigned later to be more robust. The backend is responsible for generating the download link to ensure consistency and reliability. I tried adding a divider, but the Markdown-to-Yjs conversion is very lossy and almost never handles it correctly. Only about one out of ten conversions works as expected.
2026-01-03 01:12:09 +01:00
RECORDING_DOWNLOAD_BASE_URL: https://meet.127.0.0.1.nip.io/recording
🔐(helm) configure Brevo marketing tool Using VaultWarden, added a dev Brevo API key. In the "dev" stack, enable Brevo to validate new users are signed-up to the marketing emails.
2025-01-13 21:21:16 +01:00
SIGNUP_NEW_USER_TO_MARKETING_EMAIL: True
BREVO_API_KEY:
secretKeyRef:
name: backend
key: BREVO_API_KEY
BREVO_API_CONTACT_LIST_IDS: 8
✨(backend) add 10-digit PIN codes on rooms for telephony Enable users to join rooms via SIP telephony by: - Dialing the SIP trunk number - Entering the room's PIN followed by '#' The PIN code needs to be generated before the LiveKit room is created, allowing the owner to send invites to participants in advance. With 10-digit PINs (10^10 combinations) and a large number of rooms (e.g., 1M), collisions become statistically inevitable. A retry mechanism helps reduce the chance of repeated collisions but doesn't eliminate the overall risk. With 100K generated PINs, the probability of at least one collision exceeds 39%, due to the birthday paradox. To scale safely, we’ll later propose using multiple trunks. Each trunk will handle a separate PIN namespace, and the combination of trunk_id and PIN will ensure uniqueness. Room assignment will be evenly distributed across trunks to balance load and minimize collisions. Following XP principles, we’ll ship the simplest working version of this feature. The goal is to deliver value quickly without over-engineering. We’re not solving scaling challenges we don’t currently face. Our production load is around 10,000 rooms — well within safe limits for the initial implementation. Discussion points: - The `while` loop should be reviewed. Should we add rate limiting for failed attempts? - A systematic existence check before `INSERT` is more costly for a rare event and doesn't prevent race conditions, whereas retrying on integrity errors is more efficient overall. - Should we add logging or monitoring to track and analyze collisions? I tried to balance performance and simplicity while ensuring the robustness of the PIN generation process.
2025-05-13 10:41:47 +02:00
ROOM_TELEPHONY_ENABLED: True
⬆️(docker) upgrade backend image to python 3.13 Python 3.13 is now stable, our libraries are compatible with it. We also upgrade the alpine version and node one used in the backend.
2025-06-23 14:28:54 +02:00
SSL_CERT_FILE: /usr/local/lib/python3.13/site-packages/certifi/cacert.pem
🛂(backend) disallow unregistered rooms Require users to create a room in the database before requesting a LiveKit token. If user request an access token for a room that doesn't exist in our db, its request would end in a 404 error. Ensure that rooms must be registered by a user before they can be accessed. By default, all created rooms remain public, allowing anonymous users to join any room created by a logged-in user. However, anonymous users cannot create rooms themselves.
2024-07-26 00:41:17 +02:00
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
migrate:
command:
- "/bin/sh"
- "-c"
- |
🔥(backend) remove demo data generation from tilt migration job Remove call to generate demo data in tilt stack as it was never useful to developers and only complicated the migration job unnecessarily. Migration job should be laser focused on applying database migrations rather than seeding mock data, improving clarity and reducing complexity.
2025-08-25 17:02:07 +02:00
python manage.py migrate --no-input
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
restartPolicy: Never
command:
- "gunicorn"
- "-c"
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
- "/usr/local/etc/gunicorn/meet.py"
- "meet.wsgi:application"
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
- "--reload"
createsuperuser:
command:
- "/bin/sh"
- "-c"
- |
python manage.py createsuperuser --email admin@example.com --password admin
restartPolicy: Never
✨(tilt) add missing certificate authority for Python Avoid disabling SSL verification in development environment, simply mount in the right folder, an extra volume, that declares the certificate authority necessary to validate nip.io domains.
2025-01-13 17:19:28 +01:00
# Extra volume mounts to manage our local custom CA and avoid to set ssl_verify: false
extraVolumeMounts:
- name: certs
⬆️(docker) upgrade backend image to python 3.13 Python 3.13 is now stable, our libraries are compatible with it. We also upgrade the alpine version and node one used in the backend.
2025-06-23 14:28:54 +02:00
mountPath: /usr/local/lib/python3.13/site-packages/certifi/cacert.pem
✨(tilt) add missing certificate authority for Python Avoid disabling SSL verification in development environment, simply mount in the right folder, an extra volume, that declares the certificate authority necessary to validate nip.io domains.
2025-01-13 17:19:28 +01:00
subPath: cacert.pem
# Extra volumes to manage our local custom CA and avoid to set ssl_verify: false
extraVolumes:
- name: certs
configMap:
name: certifi
items:
- key: cacert.pem
path: cacert.pem
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
frontend:
envVars:
🔧(frontend) make app title customizable with env variable override Replace default "visio" with "LaSuite Meet" and allow env variable customization. Default Docker image uses "LaSuite Meet", but deployments can override with custom values by setting env vars and rebuilding.
2025-06-06 21:57:57 +02:00
VITE_APP_TITLE: "LaSuite Meet"
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
VITE_PORT: 8080
VITE_HOST: 0.0.0.0
🔧(frontend) refactor API URl to work for remote environments Discussed IRL with @manuhabitela. In developpement, we build locally the Docker image. Thus, we can pass values to the frontend before the npm build command was called. Environment variables are great for configuration, and work perfectly in dev mode, building Docker image on the fly. However, in other environment (e.g. staging, pre-prod, prod) we'll pull a common Docker image published in a remote registry. All cited environments should use the same Docker image to make tests/deployment reproducible between envs. As the Docker image is not rebuilt on the fly, we cannot easily configure customized environment variables for each environment. The API base URL would have a different value for each environment, and would require a different environment variable. Inspired by Impress works, if no environment variable is passed for the API URL, the window origin will be used, and then the API path will be appended. Frontend and backend are always deployed on the same URL, usually frontend is at the '/' route, and backend at the '/api/vXX/' route. If any configuration are required for each remote environment, they would be retrieved from the API at runtime. Voila! Don't hesitate to challenge this commit.
2024-07-10 20:50:40 +02:00
VITE_API_BASE_URL: https://meet.127.0.0.1.nip.io/
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
replicas: 1
image:
🚚(DockerHub) rename DockerHub images I have created two new repositories on DockerHub, one for the currently existing backend image, and one for the future frontend image. I searched-replaced all occurences of "lasuite/impress-frontend" or "lasuite/impress-backend". One image won't exist anymore, "impress-y-webrtc-signaling", I have removed the steps building and pushing its image to the DockerHub account.
2024-07-01 18:32:29 +02:00
repository: localhost:5001/meet-frontend
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
pullPolicy: Always
tag: "latest"
ingress:
enabled: true
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
host: meet.127.0.0.1.nip.io
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
ingressAdmin:
enabled: true
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
host: meet.127.0.0.1.nip.io
📈(frontend) setup a reverse proxy for analytics Proxy analytics requests through our backend to minimize ad-blockers impact. I configured the Helm Charts following PostHog official documentation.
2024-09-23 11:44:20 +02:00
posthog:
ingress:
enabled: false
♻️(helm) separate PostHog ingress Based on feedback from @rouja, I've updated the Helm configuration for PostHog to use separate ingress resources for each service. Although the documentation suggests sharing the same ingress, the services have different externalName values, which conflicts with the use of a vhost in the ingress annotations. This change ensures proper service redirection by aligning each service with its own ingress.
2024-09-25 10:28:14 +02:00
ingressAssets:
enabled: false
💩(summary) kubernitize the micro service Add the micro service to the helm chart.
2024-11-25 16:01:09 +01:00
summary:
replicas: 1
envVars:
APP_NAME: summary-microservice
APP_API_TOKEN: password
AWS_STORAGE_BUCKET_NAME: meet-media-storage
AWS_S3_ENDPOINT_URL: minio.meet.svc.cluster.local:9000
AWS_S3_ACCESS_KEY_ID: meet
AWS_S3_SECRET_ACCESS_KEY: password
AWS_S3_SECURE_ACCESS: False
🔧(backend) rename OpenAI settings to WhisperX to avoid confusion Rename incorrectly named OpenAI configuration settings since they're used to instantiate WhisperX client which is not OpenAI compatible, preventing confusion about actual service dependencies.
2025-09-09 18:21:22 +02:00
WHISPERX_API_KEY: your-secret-value
WHISPERX_BASE_URL: https://configure-your-url.com
WHISPERX_ASR_MODEL: large-v2
✨(summary) introduce summary logic for meeting transcripts Implement summarization functionality that processes completed meeting transcripts to generate concise summaries. First draft base on a simple recursive agentic scenario. Observability and evaluation will be added in the next PRs.
2025-09-09 22:16:21 +02:00
LLM_BASE_URL: https://configure-your-url.com
LLM_API_KEY: your-secret-value
LLM_MODEL: meta-llama/Llama-3.1-8B-Instruct
💩(summary) kubernitize the micro service Add the micro service to the helm chart.
2024-11-25 16:01:09 +01:00
WEBHOOK_API_TOKEN: password
WEBHOOK_URL: https://www.mock-impress.com/webhook/
CELERY_BROKER_URL: redis://default:pass@redis-master:6379/1
CELERY_RESULT_BACKEND: redis://default:pass@redis-master:6379/1
image:
repository: localhost:5001/meet-summary
pullPolicy: Always
tag: "latest"
command:
- "uvicorn"
- "summary.main:app"
- "--host"
- "0.0.0.0"
- "--port"
- "8000"
- "--reload"
🔧(helm) configure Celery workers for summary microservice in Helm Add Celery summarize and transcribe worker configuration to Helm charts for summary microservice. Create new deployment resources and increment chart version to support distributed task processing.
2025-09-18 01:44:16 +02:00
celeryTranscribe:
💩(summary) kubernitize the micro service Add the micro service to the helm chart.
2024-11-25 16:01:09 +01:00
replicas: 1
envVars:
APP_NAME: summary-microservice
APP_API_TOKEN: password
AWS_STORAGE_BUCKET_NAME: meet-media-storage
AWS_S3_ENDPOINT_URL: minio.meet.svc.cluster.local:9000
AWS_S3_ACCESS_KEY_ID: meet
AWS_S3_SECRET_ACCESS_KEY: password
AWS_S3_SECURE_ACCESS: False
🔧(backend) rename OpenAI settings to WhisperX to avoid confusion Rename incorrectly named OpenAI configuration settings since they're used to instantiate WhisperX client which is not OpenAI compatible, preventing confusion about actual service dependencies.
2025-09-09 18:21:22 +02:00
WHISPERX_API_KEY: your-secret-value
WHISPERX_BASE_URL: https://configure-your-url.com
WHISPERX_ASR_MODEL: large-v2
✨(summary) introduce summary logic for meeting transcripts Implement summarization functionality that processes completed meeting transcripts to generate concise summaries. First draft base on a simple recursive agentic scenario. Observability and evaluation will be added in the next PRs.
2025-09-09 22:16:21 +02:00
LLM_BASE_URL: https://configure-your-url.com
LLM_API_KEY: your-secret-value
LLM_MODEL: meta-llama/Llama-3.1-8B-Instruct
💩(summary) kubernitize the micro service Add the micro service to the helm chart.
2024-11-25 16:01:09 +01:00
WEBHOOK_API_TOKEN: password
WEBHOOK_URL: https://www.mock-impress.com/webhook/
CELERY_BROKER_URL: redis://default:pass@redis-master:6379/1
CELERY_RESULT_BACKEND: redis://default:pass@redis-master:6379/1
🔧(helm) configure Celery workers for summary microservice in Helm Add Celery summarize and transcribe worker configuration to Helm charts for summary microservice. Create new deployment resources and increment chart version to support distributed task processing.
2025-09-18 01:44:16 +02:00
TASK_TRACKER_REDIS_URL: redis://default:pass@redis-master:6379/1
💩(summary) kubernitize the micro service Add the micro service to the helm chart.
2024-11-25 16:01:09 +01:00
image:
repository: localhost:5001/meet-summary
pullPolicy: Always
tag: "latest"
command:
- "celery"
- "-A"
♻️(summary) reorganize API code I totally reorganized the API code, to gain in clarity.
2024-11-30 00:17:12 +01:00
- "summary.core.celery_worker"
💩(summary) kubernitize the micro service Add the micro service to the helm chart.
2024-11-25 16:01:09 +01:00
- "worker"
- "--pool=solo"
- "--loglevel=info"
🔧(helm) configure Celery workers for summary microservice in Helm Add Celery summarize and transcribe worker configuration to Helm charts for summary microservice. Create new deployment resources and increment chart version to support distributed task processing.
2025-09-18 01:44:16 +02:00
- "-Q transcribe-queue"
celerySummarize:
replicas: 1
envVars:
APP_NAME: summary-microservice
APP_API_TOKEN: password
AWS_STORAGE_BUCKET_NAME: meet-media-storage
AWS_S3_ENDPOINT_URL: minio.meet.svc.cluster.local:9000
AWS_S3_ACCESS_KEY_ID: meet
AWS_S3_SECRET_ACCESS_KEY: password
AWS_S3_SECURE_ACCESS: False
WHISPERX_API_KEY: your-secret-value
WHISPERX_BASE_URL: https://configure-your-url.com
WHISPERX_ASR_MODEL: large-v2
LLM_BASE_URL: https://configure-your-url.com
LLM_API_KEY: your-secret-value
LLM_MODEL: meta-llama/Llama-3.1-8B-Instruct
WEBHOOK_API_TOKEN: password
WEBHOOK_URL: https://www.mock-impress.com/webhook/
CELERY_BROKER_URL: redis://default:pass@redis-master:6379/1
CELERY_RESULT_BACKEND: redis://default:pass@redis-master:6379/1
TASK_TRACKER_REDIS_URL: redis://default:pass@redis-master:6379/1
image:
repository: localhost:5001/meet-summary
pullPolicy: Always
tag: "latest"
command:
- "celery"
- "-A"
- "summary.core.celery_worker"
- "worker"
- "--pool=solo"
- "--loglevel=info"
- "-Q summarize-queue"
✨(backend) add authenticated recording file access method Implement secure recording file access through authentication instead of exposing S3 bucket or using temporary signed links with loose permissions. Inspired by docs and @spaccoud's implementation, with comprehensive viewset checks to prevent unauthorized recording downloads. The ingress reserved to media intercept the original request, and thanks to Nginx annotations, check with the backend if the user is allowed to donwload this recording file. This might introduce a dependency to Nginx in the project by the way. Note: Tests are integration-based rather than unit tests, requiring minio in the compose stack and CI environment. Implementation includes known botocore deprecation warnings that per GitHub issues won't be resolved for months.
2025-04-14 16:41:49 +02:00
ingressMedia:
enabled: true
host: meet.127.0.0.1.nip.io
annotations:
nginx.ingress.kubernetes.io/auth-url: https://meet.127.0.0.1.nip.io/api/v1.0/recordings/media-auth/
nginx.ingress.kubernetes.io/auth-response-headers: "Authorization, X-Amz-Date, X-Amz-Content-SHA256"
nginx.ingress.kubernetes.io/upstream-vhost: minio.meet.svc.cluster.local:9000
nginx.ingress.kubernetes.io/rewrite-target: /meet-media-storage/$1
serviceMedia:
host: minio.meet.svc.cluster.local
port: 9000
Reference in New Issue Copy Permalink