Note: I am not affiliated with this project in any way. I think it’s a very promising alternative to things like MinIO and deserves more attention.

21 points

What’s the difference between this and minio?

permalink
report
reply
17 points

I remember when minio just started and it was small and easy to run. Nowadays, it’s a full-blown enterprise product, though, full of features you’ll never care about in a homelab eating on your cpu and ram.

Garage is small and easy to run. I’ve been toying with it for several months and I’m more than happy with its simple API and tiny footprint. I even run my (static html) blog off it because it’s just easier to deploy it to a S3-compatible API.

permalink
report
parent
reply
10 points

Minio now describes itself as “S3 & Kubernetes Native Object Storage for AI” - lol

Guess it’s time to look for alternatives if you’re not doing ML stuff

permalink
report
parent
reply
4 points

Of course it does AI now!

But seriously, the easiest guide for minio setup meant using their operator. The garage guide was: spin up this single deploy and it works from there.

permalink
report
parent
reply
2 points

S3 storage is simpler than local files? I think you need to elaborate

permalink
report
parent
reply
2 points

S3 storage is simpler than running scp -r to a remote node, because you can copy files to S3 in a massively parallel way and scp is generally sequential. It’s very easy to protect the API too, as it’s just HTTP (and at it, it’s also significantly faster than WebDAV).

permalink
report
parent
reply
2 points

It is simpler when you’re doing stuff on the web and/or need to scale.

permalink
report
parent
reply
10 points

Minio is definitely not designed to be self hosted on a small server by normal people but more for enterprise use where you have multiple servers and you’re paying hundreds of thousands of dollars for support

permalink
report
parent
reply
3 points

Minio didnt need a container rig crutch to lean on when I last looked at it.

permalink
report
parent
reply
5 points

I‘m currently trying to bring up a rather complicated setup using garage. Garage on Homeserver behind firewall, vpn relay, peertube and other s3 compatible services on a vps. Garage works rather weill, the vpn is giving me a hard time though. Can recommend.

permalink
report
reply
4 points

Thoughts on this vs postgres blob storage? I know they aren’t the same thing.

permalink
report
reply
9 points

Buckets have a lot of features that postgres don’t. Like mounting via FUSE. And Garage in particular offers some integrations to apps, websited, and so on. I would go with this instead of having a column of byte data in a DB table. The pgsql solution might work in small and simple cases (e.g. storing the user’s avatar in a forum) but even so, if I could or had to choose, I wouldn’t do it.

permalink
report
parent
reply
4 points

Great points.

For isolated projects in the past I’ve had great success storing things in postgres,. (generally large documents that are relationally tied to other more traditional PG data, in a db driven project) Just saying size and recall have been pretty happy.

As you say the other features are distinguishing.

permalink
report
parent
reply
4 points

I’m always personally wary of storing blobs in a database if for no other reason it’s going to totally be more expensive to store on a server rather than in some sort of blob storage.

permalink
report
parent
reply
4 points

Has anyone tried it? I am thinking about using it on some Raspberry Pi 5.

permalink
report
reply
4 points

Has anyone compared it against seaweedfs?

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 1.8K

    Posts

  • 18K

    Comments