Compare commits

..
4 changed files with 10 additions and 29 deletions
+2 -17
View File
@@ -4,21 +4,7 @@ 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.
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.
## Become a maintainer
@@ -26,5 +12,4 @@ 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).
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).
+1 -4
View File
@@ -39,14 +39,11 @@ 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
+7 -7
View File
@@ -64,14 +64,14 @@ x-postgres-env: &postgres-env
services:
app:
image: lasuite/meet-frontend:v1.37.0
image: lasuite/meet-frontend:v1.35.0
networks:
- backend
deploy:
labels:
- "traefik.enable=false"
- "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
- "coop-cloud.${STACK_NAME}.version=0.9.0+v1.37.0"
- "coop-cloud.${STACK_NAME}.version=0.7.0+v1.31.0"
user: "${DOCKER_USER:-1000}"
entrypoint:
- /docker-entrypoint.sh
@@ -87,7 +87,7 @@ services:
start_period: 10s
backend:
image: lasuite/meet-backend:v1.37.0
image: lasuite/meet-backend:v1.35.0
networks:
- backend
environment:
@@ -119,7 +119,7 @@ services:
- email_pass
celery:
image: lasuite/meet-backend:v1.37.0
image: lasuite/meet-backend:v1.35.0
networks:
- backend
healthcheck:
@@ -173,7 +173,7 @@ services:
- postgres_p
redis:
image: redis:8.10.3
image: redis:8.10.2
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 15s
@@ -183,7 +183,7 @@ services:
- backend
livekit:
image: livekit/livekit-server:v1.13.11
image: livekit/livekit-server:v1.13.10
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.8
image: nginx:1.31.7
environment:
- STACK_NAME
healthcheck:
-1
View File
@@ -1 +0,0 @@
Latest security updates