MinIO Community version 2.0 is going back to be an object browser only
github.comIn a move that reminiscent of the change of Redis, they removed all the functionality of the UI of the community version and pointed to the paid version.
From the Changelog: (https://github.com/minio/object-browser/blob/master/CHANGELO...)
"Deprecated support of accounts & policies management, this can be managed by using mc admin commands.
Deprecated support of bucket management, this can be managed by using mc commands.
Deprecated support of configuration management, this can be managed by using mc admin config commands. Please refer to the MinIO Client for more information.Deprecated support of accounts & policies management, this can be managed by using mc admin commands.
Deprecated support of bucket management, this can be managed by using mc commands.
Deprecated support of configuration management, this can be managed by using mc admin config commands. "
This PR that removes away all the features in the UI: https://github.com/minio/object-browser/pull/3509 . The discussion around this PR is locked.
I think that "Deprecated support" has another meaning. I hate when this kind of things happens.
Oh good I'll look forward to migrating away from this in the near future then.
Someone is already forked to the last version befote changes [1] but not sure about the potential project future or if it is going to gain traction.
Also any alternative that people are using that is similar?
Which software are folks using to run self-hosted / on-premises S3? I'm looking to replace MinIO in my homelab and would like to keep a S3 management UI.
Some that I've seen:
SeaweedFS: https://github.com/seaweedfs/seaweedfs (Apache 2.0)
Garage: https://git.deuxfleurs.fr/Deuxfleurs/garage (AGPL)
Zenko: https://github.com/scality/Zenko (Apache 2.0)
But which ones have a management UI?
None of those, if a quick search of "ui/gui/user experience" is of any indication.
Also looking for an alternative to MinIO since I also rely on the GUI for some things. But it feels like these things should probably be separate? Since they all expose a S3 compatible API interface, couldn't we have one GUI that can be used regardless of the backend?
It's great when building software and testing locally, e.g. in a docker setup.
Bear in mind that actual features are NOT going away, it's just the web-based UI that has been removed with `mc` command staying intact.
> Bear in mind that actual features are NOT going away
To many of us, having a UI is an actual feature, in so much that if there are alternatives to MinIO that comes with a UI, I'd probably move to that.
It's an odd direction to take too.
I can see an individual or very small team using the web based GUI, but a large enterprise client would need automation that's done via the cli.
I think the changelog is pretty clear on that, but I assume for many users this is not a "just" thing and matters a lot. Enshittification started before this change, but now it's really obvious where they are heading.
In my personal opinion, this is a perfectly fine change. The company has to make money. Nudging corporate users (who are incapable of running `mc`) towards purchase of license to have a web UI is a nice solution, I'm all for it.
why mc is needed at all? can't one just use aws s3 CLI with environment variable pointing to MinIO S3 backend endpoint?
You can't create tenants with AWS s3 CLI
Discussion on reddit: https://www.reddit.com/r/selfhosted/comments/1kva3pw/avoid_m...
Clinking silverware heard in the distance