chore: publish 0.9.0+v1.37.0 release

When I follow the instructions but *don't* specify the Redirect URI - and then go to my Meet domain, I just get an error that the redirect uri is invalid.

Also moved Client authentication higher up to match the layout of keycloak's UI.

Signed-off-by: Sarma <131+amras@noreply.git.coopcloud.tech>

MAINTENANCE.md

@@ -0,0 +1,30 @@
+# Lasuite-Meet Recipe Maintenance
+
+All contributions should be made via pull requests.
+
+## Pull Requests
+
+A pull request can be merged directly into `main` by any maintainer. 
+No approval is needed, but pull requests should be tested as working before merge.
+
+## Dependency Updates
+
+- patch updates proposed from renovate bot are merged directly - 
+  if there is a CVE, also release a new patch version of this recipe
+- minor updates proposed from renovate bot are tested by one maintainer 
+  and merged if they don't break, then a new minor version of the recipe 
+  is released
+- major updates proposed form renovate bot are tested by two maintainers 
+  and merged if they don't break, then a major version of the recipe is 
+  released. 
+  If the renovate bot PR is older than one week, one maintainer can decide
+  to merge it anyway. 
+
+## Become a maintainer
+
+Everyone can apply to be a recipe maintainer:
+
+1. Watch the repository to get updates.
+2. Add yourself to the list in [README.md](./README.md) and open a pull request with the change.
+3. Once the pull request is merged, you will be added to the 
+  [La Suite maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/lasuite-maintainers).

README.md

@@ -3,7 +3,7 @@
 > [Meet](https://github.com/suitenumerique/meet) (part of [La Suite Numerique](https://lasuite.numerique.gouv.fr/en)) for Co-op Cloud
 
 <!-- metadata -->
-
+* **Maintainer**: [@trav](https://git.coopcloud.tech/trav), [@notplants](https://git.coopcloud.tech/notplants), [@ineiti](https://git.coopcloud.tech/ineiti)
 * **Category**: Apps
 * **Status**: 2, beta
 * **Image**: [`lasuite/meet-backend`](https://hub.docker.com/r/lasuite/meet-backend), 4, upstream
@@ -39,11 +39,14 @@ Instructions for integrating keycloak with meet after deploying it, are below.
 * In keycloak, create a realm (save the name of this realm, you will need it later)
 * Within that realm, create a client
     * during client creation, ensure:
+        - Client authentication: True
         - Standard flow: True
         - Direct access grants: True
         - Authorization: True
-        - Client authentication: True
         - PKCE method: none
+        - Valid Redirect URIs: `https://<your-meet-domain>/api/v1.0/callback/` (don't forget the trailing slash)
+        - Home URL: `https://<your-meet-domain>/`
+        - Root URL: `https://<your-meet-domain>/`
 * Within the client tab, for your client, click on "Credentials". Click on the copy button to copy "Client Secret" so you can insert this into your coop cloud deployment in the next step.
 * `abra app secret insert <app-name> oidc_rpcs v2 <yoursecret>`
 * `abra app config <app-name>` # set SECRET_OIDC_RPCS_VERSION=v2
@@ -141,7 +144,3 @@ The warning should be gone from the LiveKit boot log.
 TURN is enabled by default and helps users behind CGNAT/symmetric NAT connect to video calls. To disable it, remove `compose.turn.yml` from `COMPOSE_FILE` in your app config and set `LIVEKIT_TURN_ENABLED=false`.
 
 See `docs/multinode.md` for multi-node deployment considerations.
-
-## Maintainers
-
-coop cloud recipe maintained by @notplants

compose.yml

@@ -64,14 +64,14 @@ x-postgres-env: &postgres-env
 
 services:
   app:
-    image: lasuite/meet-frontend:v1.19.0
+    image: lasuite/meet-frontend:v1.37.0
     networks:
       - backend
     deploy:
       labels:
         - "traefik.enable=false"
         - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
-        - "coop-cloud.${STACK_NAME}.version=0.4.0+v1.19.0"
+        - "coop-cloud.${STACK_NAME}.version=0.9.0+v1.37.0"
     user: "${DOCKER_USER:-1000}"
     entrypoint:
       - /docker-entrypoint.sh
@@ -87,7 +87,7 @@ services:
       start_period: 10s
 
   backend:
-    image: lasuite/meet-backend:v1.19.0
+    image: lasuite/meet-backend:v1.37.0
     networks:
       - backend
     environment:
@@ -119,7 +119,7 @@ services:
       - email_pass
 
   celery:
-    image: lasuite/meet-backend:v1.19.0
+    image: lasuite/meet-backend:v1.37.0
     networks:
       - backend
     healthcheck:
@@ -173,7 +173,7 @@ services:
       - postgres_p
 
   redis:
-    image: redis:8.6.4
+    image: redis:8.10.3
     healthcheck:
       test: ["CMD", "redis-cli", "ping"]
       interval: 15s
@@ -183,7 +183,7 @@ services:
       - backend
 
   livekit:
-    image: livekit/livekit-server:v1.12.0
+    image: livekit/livekit-server:v1.13.11
     command: --config /livekit-server.yaml
     environment:
       - STACK_NAME
@@ -223,7 +223,7 @@ services:
         - "traefik.http.services.${STACK_NAME}_livekit.loadbalancer.server.port=7880"
 
   web:
-    image: nginx:1.31.1
+    image: nginx:1.31.8
     environment:
       - STACK_NAME
     healthcheck:

release/0.8.2+v1.36.3

@@ -0,0 +1 @@
+Latest security updates