Merge pull request 'Update maintainers' (#15) from update_maintainers into main

Reviewed-on: #15

MAINTENANCE.md

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

@@ -3,7 +3,7 @@
 > [Drive](https://github.com/suitenumerique/drive) (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
 * **Image**: [`lasuite/drive`](https://hub.docker.com/r/lasuite/drive), 4, upstream
@@ -92,8 +92,3 @@ You then need to insert the password for your smtp server as a secret:
 Then redeploy the app, and automated e-mail sending should work:
 
 `abra app deploy <app-name> --force`
-
-
-## Maintainers
-
-coop cloud recipe maintained by @notplants

compose.yml

@@ -102,7 +102,7 @@ services:
       labels:
         - "traefik.enable=false"
         - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
-        - "coop-cloud.${STACK_NAME}.version=0.13.0+v0.22.0"
+        - "coop-cloud.${STACK_NAME}.version=0.13.2+v0.22.0"
     environment:
       <<: [ *common-env ]
     healthcheck:
@@ -229,7 +229,8 @@ services:
       - backend
 
   minio:
-    image: quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z
+    image: bitnamilegacy/minio:2025.7.23-debian-12-r5
+    user: root
     environment: *minio-env
     healthcheck:
       test: ["CMD", "mc", "ready", "local"]
@@ -239,11 +240,11 @@ services:
     networks:
       - backend
       - proxy
-    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
     configs:
       - source: abra_entrypoint
         target: /abra-entrypoint.sh

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-drive-init
+
 # Wait for minio to be ready (up to 60 seconds)
 i=0
 while ! mc ready local 2>/dev/null; do