From 74c06a196a8d434c0be416c5d0bd9696a17e376d Mon Sep 17 00:00:00 2001 From: Renovate Bot Date: Tue, 10 Mar 2026 17:50:52 +0000 Subject: [PATCH 1/4] Add renovate.json --- renovate.json | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 renovate.json diff --git a/renovate.json b/renovate.json new file mode 100644 index 0000000..5db72dd --- /dev/null +++ b/renovate.json @@ -0,0 +1,6 @@ +{ + "$schema": "https://docs.renovatebot.com/renovate-schema.json", + "extends": [ + "config:recommended" + ] +} From 4f9cb564694a26afe4f74af11a4068d0ec31e9b1 Mon Sep 17 00:00:00 2001 From: Linus Gasser Date: Tue, 29 Sep 2026 07:41:41 +0200 Subject: [PATCH 2/4] Update to minio from bitnamilegacy --- compose.yml | 9 +++++---- minio-initialize.sh | 5 +++++ 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/compose.yml b/compose.yml index 8539a24..46fc16c 100644 --- a/compose.yml +++ b/compose.yml @@ -253,7 +253,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"] @@ -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}" diff --git a/minio-initialize.sh b/minio-initialize.sh index 3511083..f0f552e 100644 --- a/minio-initialize.sh +++ b/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 From 9f3d9588a21fd8e8b71dde48e1a599e3afbb25b4 Mon Sep 17 00:00:00 2001 From: notplants <@notplants> Date: Tue, 29 Sep 2026 10:04:09 -0400 Subject: [PATCH 3/4] chore: publish 0.4.3+v5.6.1 release --- compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compose.yml b/compose.yml index 46fc16c..3015562 100644 --- a/compose.yml +++ b/compose.yml @@ -110,7 +110,7 @@ services: labels: - "traefik.enable=false" - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}" - - "coop-cloud.${STACK_NAME}.version=0.4.2+v5.6.1" + - "coop-cloud.${STACK_NAME}.version=0.4.3+v5.6.1" user: "${DOCKER_USER:-1000}" healthcheck: test: ["CMD", "curl", "-f", "http://localhost:8080"] From 25db1d6790efbef342c0940a37f0d2d864ba5b33 Mon Sep 17 00:00:00 2001 From: notplants <@notplants> Date: Tue, 29 Sep 2026 14:26:16 +0000 Subject: [PATCH 4/4] docs: add recipe maintenance policy --- MAINTENANCE.md | 15 +++++++++++++++ README.md | 5 +++++ 2 files changed, 20 insertions(+) create mode 100644 MAINTENANCE.md diff --git a/MAINTENANCE.md b/MAINTENANCE.md new file mode 100644 index 0000000..5e6ae11 --- /dev/null +++ b/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). diff --git a/README.md b/README.md index 49e32b7..9c0a435 100644 --- a/README.md +++ b/README.md @@ -80,3 +80,8 @@ 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 --force` + +## Maintainers + +* @trav +* @notplants