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.
What’s the difference between this and minio?
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.
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
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.
S3 storage is simpler than local files? I think you need to elaborate
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).
Nobody should be using SCP, use rsync.
S3 goes beyond the scope you describe. You disqualify yourself with such statements
Clearly I mean Garage in here when I write “S3.” It is significantly easier and faster to run
hugo deployand let it talk to Garage, then to figure out where on a remote node the nginx k8s pod has its data PV mounted and scp files into it. Yes, I could automate that. Yes, I could pin the blog’s pod to a single node. Yes, I could use a stable host path for that and use rsync, and I could skip the whole kubernetes insanity for a static html blog.But I somewhat enjoy poking the tech and yes, using Garage makes deploys faster and it provides me a stable well-known API endpoint for both data transfers and for serving the content, with very little maintenance required to make it work.
I don’t follow. S3 is an AWS service that these tools emulate locally by providing the same API. But I’m happy to accept that there’s just some misunderstanding 😃
In the context of my comments here, any mention of “S3” means “S3-compatible” in the way that’s implemented by Garage. I hope that clarifies it for you.
It is simpler when you’re doing stuff on the web and/or need to scale.
I disagree. Local files access is always superior. If you disagree, your target solution is likely poor to begin with
This is such a poor attempt at trolling. Don’t you have better things to do?
Bro, I’m an AWS Cloud Solution Architect and I seriously don’t know what you’re talking about. And, no, when I waste time on Lemmy, then there is literally nothing better to do.
AWS made S3. People built software to integrate S3 as a storage backend. Other people didn’t want to do AWS, and built single-node imitations of the S3 service. Now you use those services and think that is S3, while it is only a crude replica of what S3 really is. At this point the S3 API is redundant and you could just as well store your assets close to your application. You have no real, global S3 delivery service anyway. What’s the point?
Most people misuse AWS S3. Using stuff like minio is even more misguided.
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
Minio didnt need a container rig crutch to lean on when I last looked at it.
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.
Has anyone tried it? I am thinking about using it on some Raspberry Pi 5.
Has anyone compared it against seaweedfs?
Thoughts on this vs postgres blob storage? I know they aren’t the same thing.
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.
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.
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.
I have been mostly happy with minio but the setup and update process are a bit painful so next time I find myself annoyed with it I might have to give this a shot.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters HTTP Hypertext Transfer Protocol, the Web SCP Secure Copy encrypted file transfer tool, authenticates and transfers over SSH SSH Secure Shell for remote terminal access k8s Kubernetes container management package nginx Popular HTTP server
4 acronyms in this thread; the most compressed thread commented on today has 20 acronyms.
[Thread #875 for this sub, first seen 17th Jul 2024, 21:55] [FAQ] [Full list] [Contact] [Source code]
So it compares to existing products, but it’s less mature? Why should anyone care?
Compared to MinIO, it has more storage backend flexibility, cross-region replication is easy, it is resilient to less-than-ideal network conditions between nodes. Did you bother reading the website?
I’m not sure why your immediate reaction to having more options is negative.
