Was pretty much clear since last year. At the latest in December when they switched to “maintenance mode”. And now they archived it.
https://blog.vonng.com/en/db/minio-is-dead/
Alternatives include Garage, SeaweedFS and RustFS.
Garage seems like a viable alternative.
Garage has been great in my homelab. It’s not quite as 1:1 with S3 but it does all the basics with some really nice features.
+1 to Garage being great! I used it for a personal project and it worked really well. A lot of S3 data browsing clients also support it natively or just through API compatibility too
They’ve been anti-open source for a while, they clearly don’t see a profit motive without killing off their open source side. Anyone selfhosting or into open source should consider MinIO dead, and migrate. Hopefully someone forks it.
Hopefully someone forks it.
people did, and then proceeded to do nothing with it.
I don’t like minio’s moves here or the way they communicated it but they weren’t wrong when they said the community was not contributing in a significant way.
S3 compatibility is nice I guess if you need S3 compatibility but also… why would you need that?
sshfs does everything I need and compatibility is almost native.
SSHFS is a hack and has nothing to do with the proposal of S3 compatible backends
So enlighten me then, save me from my terrible hack that is working fine for me and tell me what it DOES have to do with. I thought S3 was a remote filesystem you can use, essentially Amazon’s proprietary version of webdav where you get a http bucket you can only access with aws proprietary tools. What’s the attraction? Clearly it seems like people love it, and I am getting dunked on for asking an honest question, which feels a bit unhealthy and unpleasant for the self-hosting community.
Am I supposed to be familiar with AWS infrastructure as a prerequisite for being here?
ok, to start with, if you need a POSIX interface to the filesystem, you already have an SSH connection to that server, and don’t need much stability across multiple clients, SSHFS may do just fine. For a homelab, that is likely the case.
now, if you’re hosting a web server that needs data distributed across drives/nodes, data redundancy, and the usage is primarily programmatic, closer to a CDN’s or machine learning pipeline than a single user browsing files; then you want an S3-compatible solution. The S3 API makes it easier to plug it into your application, while allowing you to migrate to a different one - which I’m actually currently doing for a MinIO deployment at work.
Sshfs has way more overhead and doesn’t do remotely the same thing
Kubernetes storage is the reason I was looking at Minio in the past.
Shit, I am actually building a webtool and thought Minio could be a good part to be a file storage in it. What’s an good alternative?
Edit: I try “garage”
There’s also SeaweedFS that I’ve used as an S3 compatible fileserver
…a hard disk? you can just write data to a file
Not if you want to validate S3 compatibility for an actual future use case or, * can you imagine*, just for the fun of it.
i’ll give you the second case, but nobody should plan for putting stuff on aws with the world as it looks right now…
I use S3 with OVH at my workplace. So it’s not just aws / google.
Genuine question, what are the alternatives not called Azure/GCP?
Sadly I only recognized it as “the thing you put in your docker compose for integration tests”.
