MinIO Losing Active Development - Update S3-like Storage

[TateWalker]

MinIO is ending active development for the self-hosted, community edition. https://linuxiac.com/minio-ends-active-development/

Need a separate solution for attachment storage from an actively maintained project.

[thecodrr]

What options do we have?

[alexanderadam]

Garage

[nicmart-dev]

Thanks, I was able to replace minio/minio:RELEASE.2024-07-29T22-14-52Z by dxflrs/garage:v2.1.0 on my Synology NAS DS425+
Tested and it seems to work across clients to attach images or other files attachments and read them. Seems self-hosted monograph won't allow me to see or download files like PDF though (but I had this issue when I had minio too so likely not due to s3 but monograph).

Here is a prompt I created, based on the Gemini chat that helped me through it from start to finish:

Role: You are an expert in Docker, Self-Hosting, and S3 Object Storage (specifically GarageHQ).

Context:
I am self-hosting Notesnook on a Synology NAS using Portainer.

• I currently use MinIO but want to migrate to GarageHQ (v2.1.0) for better performance and lower resource usage.
• My setup uses Cloudflare Tunnel for external access.
• I am running a single-node setup.

Task:
Guide me step-by-step through replacing MinIO with Garage in my docker-compose stack.

Requirements & Specific Hurdles:

1. Docker Compose: Provide the correct service block for dxflrs/garage:v2.1.0. Ensure you include a healthcheck that uses /garage status.
2. Configuration: I cannot mount a config file easily. Please provide the configuration via Environment Variables or a simple command to generate the minimal required config.
3. Initialization (The Hard Part): Since Portainer's console is not interactive, give me the exact single-line commands I need to run to:

• Initialize the layout (layout assign, layout apply).
• Create a bucket named attachments.
• Create an API key.
• Crucial: Grant the key R/W/Owner permissions to the bucket (Garage v2 syntax).
• Crucial: Enable "Website Access" on the bucket so images load in the app.

4. CORS Policy (The Fix): Garage is strict about CORS. Provide the aws-cli Docker command I can run via SSH (Synology) to force a "Permissive" CORS policy on the attachments bucket so the Notesnook web app can actually fetch the images.
5. Final Integration: Tell me exactly which variables (S3_ACCESS_KEY_ID, S3_ENDPOINT, etc.) to update in the notesnook-server service.

Goal:
A fully working Garage S3 backend where image uploads and downloads work immediately in Notesnook without "Failed to fetch" errors.

[clayauld]

See PR #79 to add details on migrating to garage and updating MongoDB to v8.

[jordanhandy]

@clayauld
Took a look at your docs. Couldn't get this to work. Garage is stuck in an infinite restart loop, so your bootstrap script fails to start because its waiting for Garage to be fully running. If you're open to troubleshoot, lmk how I can reach you.

[clayauld]

Yeah I can help troubleshoot. Do you have any logs to share? I can create a new instance to see if I can replicate the issue.

[jordanhandy]

@clayauld

I appreciate the reply. You can disregard. Issue was because I was using a docker frontend to deploy, and it wasn't respecting the location of the garage.toml file even though I had it in the correct local dir.

Because it wasn't found, garage.toml was created as a dir instead of a file on container init, so there was an error. Running compose up -d directly from the command line instead solved the issue because the file was correctly found.

Works great, and your bootstrap script made the setup super easy. Thanks

[clayauld]

Sweet! Glad you got it sorted out and it worked for you! 👍

[clayauld]

Looks like a community fork of MinIO may be the real solution here: https://github.com/pgsty/minio

I have not tested it, but this is likely the easiest migration path.