3 ms·
> 2026-03-02: Ruohang Feng has forked MinIO to pgsty/minio and is promising to maintain a stable, CVE-patched, distribution. This is what I went with. I use i
by cadamsdotcom 18d ago
> 2026-03-02: Ruohang Feng has forked MinIO to pgsty/minio and is promising to maintain a stable, CVE-patched, distribution.
This is what I went with.
I use it in end to end tests as an S3 simulator that starts and stops instantly and reads & writes to a local directory, - as you'd expect it's great in that role. No complaints. Given the fork's maintainer puts their real name on it & stakes their reputation, you'd assume it can be trusted - but my use case is simpler than most.
- samgranieri 18d agoI might have to try this. I’m currently pinned on the last non-crippled version of minio
- nacnud 18d agoAccording to https://github.com/pgsty/silo https://github.com/pgsty/silo it's pgsty/silo now: > Renamed from pgsty/minio to pgsty/silo, default branch master → main, on 2026-08-06
- spapas82 18d agoThis is what I use. I had a minio instance that was replaced flawlessly with silo. This is an excellent project and needs more traction. All existing minio users must switch to Silo ASAP.
- rietta 18d agoNeat! I had switched some projects to SeaweedFS's Docker image. It worked well. This is good to know there is a successor open source project that would require no code changes to use. Will evaluate.
- v3ss0n 13d agoThis need to go mainstream.
- imglorp 18d agoRight. It's nice to hear about other products, but OP made it sound like Minio disappeared and was not an option. Neither are true. Yes the company moved on but the old source is sitting there and that version is pretty good as-is. We're still using it in prod, no issues for us. The old container images are floating around and you're free to copy them to wherever. If you need support or newer features, fork it or use ^ this fork.