fix(deploy): pin minio-init restart and fail init loudly #120

Merged

TimCane merged 1 commit from fix/coolify-minio-init into main

2026-07-08 09:13:28 +01:00

TimCane commented

2026-07-08 09:05:53 +01:00

(Migrated from github.com)

Summary

pin restart: "no" on minio-init: coolify injects unless-stopped into policy-less services, and a restarting one-shot never satisfies service_completed_successfully - the stack start hangs at 'Starting new application'
harden the init script: quote creds (spaces survive), guard empty values, drop exit 0 so a failed init blocks app start instead of passing silently
rename the mc alias local -> deploy: mc ships a built-in local alias at localhost:9000 that masks a failed alias set with connection-refused noise
document the coolify setup path in docs/13

Test plan

dry-ran the init script with a stubbed mc: happy path exits 0, redeploy with existing ilm rule exits 0, empty creds exit nonzero with a clear message
YAML parse-checked the compose file
redeploy on coolify and confirm the stack starts and minio-init exits 0 once

## Summary - pin `restart: "no"` on `minio-init`: coolify injects `unless-stopped` into policy-less services, and a restarting one-shot never satisfies `service_completed_successfully` - the stack start hangs at 'Starting new application' - harden the init script: quote creds (spaces survive), guard empty values, drop `exit 0` so a failed init blocks app start instead of passing silently - rename the mc alias `local` -> `deploy`: mc ships a built-in `local` alias at localhost:9000 that masks a failed `alias set` with connection-refused noise - document the coolify setup path in docs/13 ## Test plan - dry-ran the init script with a stubbed `mc`: happy path exits 0, redeploy with existing ilm rule exits 0, empty creds exit nonzero with a clear message - YAML parse-checked the compose file - [ ] redeploy on coolify and confirm the stack starts and `minio-init` exits 0 once