Update maintainers

Move maintainers to metadata and add @ineiti

MAINTENANCE.md

@@ -0,0 +1,15 @@
+# Lasuite-Docs 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.
+
+## 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

@@ -4,6 +4,7 @@
 
 <!-- metadata -->
 
+* **Maintainer**: [@trav](https://git.coopcloud.tech/trav), [@notplants](https://git.coopcloud.tech/notplants), [@ineiti](https://git.coopcloud.tech/ineiti)
 * **Category**: Apps
 * **Status**: 2
 * **Image**: [`lasuite/docs`](https://hub.docker.com/r/lasuite/docs), 4, upstream

compose.yml

@@ -103,14 +103,14 @@ x-minio-env: &minio-env
 
 services:
   app:
-    image: lasuite/impress-frontend:v5.1.0
+    image: lasuite/impress-frontend:v5.6.1
     networks:
       - backend
     deploy:
       labels:
         - "traefik.enable=false"
         - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
-        - "coop-cloud.${STACK_NAME}.version=0.3.4+v5.1.0"
+        - "coop-cloud.${STACK_NAME}.version=0.4.3+v5.6.1"
     user: "${DOCKER_USER:-1000}"
     healthcheck:
       test: ["CMD", "curl", "-f", "http://localhost:8080"]
@@ -120,7 +120,7 @@ services:
       start_period: 10s
 
   backend:
-    image: lasuite/impress-backend:v5.1.0
+    image: lasuite/impress-backend:v5.6.1
     networks:
       - backend
     environment:
@@ -155,7 +155,7 @@ services:
       - email_pass
 
   celery:
-    image: lasuite/impress-backend:v5.1.0
+    image: lasuite/impress-backend:v5.6.1
     networks:
       - backend
     healthcheck:
@@ -185,7 +185,7 @@ services:
 
 
   y-provider:
-    image: lasuite/impress-y-provider:v5.1.0
+    image: lasuite/impress-y-provider:v5.6.1
     networks:
       - backend
     healthcheck:
@@ -243,7 +243,7 @@ services:
       - postgres_p
 
   redis:
-    image: redis:8.8.0
+    image: redis:8.10.1
     healthcheck:
       test: ["CMD", "redis-cli", "ping"]
       interval: 15s
@@ -253,7 +253,8 @@ services:
       - backend
 
   minio:
-    image: minio/minio:RELEASE.2025-05-24T17-08-30Z
+    image: bitnamilegacy/minio:2025.7.23-debian-12-r5
+    user: root
     environment: *minio-env
     healthcheck:
       test: ["CMD", "mc", "ready", "local"]
@@ -262,11 +263,11 @@ services:
       retries: 300
     networks:
       - backend
-    command: minio server /data
+    command: /opt/bitnami/scripts/minio/run.sh
     entrypoint: >
-      sh -c "/minio-initialize.sh & exec /usr/bin/docker-entrypoint.sh \"$$@\"" --
+      sh -c "/minio-initialize.sh & exec /opt/bitnami/scripts/minio/entrypoint.sh \"$$@\"" --
     volumes:
-      - minio:/data
+      - minio:/bitnami/minio/data
     deploy:
       labels:
         backupbot.backup: "${ENABLE_BACKUPS:-true}"
@@ -283,7 +284,7 @@ services:
       - minio_ru
 
   web:
-    image: nginx:1.31.1
+    image: nginx:1.31.5
     healthcheck:
       test: ["CMD", "curl", "-f", "http://localhost:8083"]
       interval: 15s

minio-initialize.sh

@@ -1,6 +1,11 @@
 #!/bin/sh
 set -e
 
+# Use an isolated mc config dir: the bundled Bitnami image runs its own
+# internal mc client (as the "minio" user) against the default /.mc path,
+# which collides with this script running as root against the same path.
+export MC_CONFIG_DIR=/tmp/mc-docs-init
+
 # Wait for minio to be ready (up to 60 seconds)
 i=0
 while ! mc ready local 2>/dev/null; do