infra: migrate deployment to Coolify with Garage S3
Some checks failed
CI / ci (push) Failing after 19s
CI / deploy (push) Has been skipped
CI / e2e (push) Has been skipped

- Remove docker-compose files (Coolify manages services individually)
- Replace MinIO with Garage (S3-compatible, actively maintained)
- Add CI deploy job: build+push :develop image on every green Develop push
- Add Coolify webhook trigger for automatic redeployment
- Update README, .env.example, and storage references
- Rename migrate script to provider-agnostic name

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-04-07 15:28:43 +02:00
parent 41e58d0153
commit d519a83cc4
11 changed files with 107 additions and 272 deletions

View File

@@ -1,5 +1,5 @@
/**
* One-time migration script: uploads/ -> MinIO (S3-compatible object storage)
* One-time migration script: uploads/ -> S3-compatible object storage
*
* Reads all image files from the local uploads/ directory and uploads each
* to the S3 bucket via the storage service. Preserves original filenames
@@ -7,10 +7,10 @@
*
* Prerequisites:
* - S3_ENDPOINT, S3_ACCESS_KEY, S3_SECRET_KEY env vars must be set
* - The S3 bucket must exist (created by docker-compose or manually)
* - The S3 bucket must exist
*
* Usage:
* bun run scripts/migrate-images-to-minio.ts
* bun run scripts/migrate-images-to-s3.ts
*/
import { readdir } from "node:fs/promises";