jo-chemla commented on issue #47908: URL: https://github.com/apache/arrow/issues/47908#issuecomment-4631947577
pgsty/minio community fork focus is indeed focused on maintaining that fork, fixing CVEs, console and docs brought back, not adding new features. There is strong community awareness at 1.6k github stars, and it's your call to decide whether it will be preferrable to switch to another viable, future-proof, `well-maintained and widely used` alternative like [rustfs](https://github.com/rustfs/rustfs), [deuxfleurs/garage](https://garagehq.deuxfleurs.fr/) or [seaweedfs](https://github.com/seaweedfs/seaweedfs) already cited in the thread and often surfaced as post-minio-era alternatives. Quick quote below note from pgsty/miino readme, > This is a community-maintained fork of [minio/docs](https://github.com/minio/docs) , maintained by [Pigsty](https://pigsty.io/) at [pgsty/minio-docs](https://github.com/pgsty/minio-docs) . This project is not affiliated with, endorsed by, or sponsored by MinIO, Inc. “MinIO” is a trademark of MinIO, Inc., used here solely to identify the upstream project. > > Changes from upstream are minimal: > > - Restored the embedded management console version reference > - Updated documentation links and Go module paths to point to this repository > - Distributed under the original [GNU AGPLv3](https://github.com/pgsty/minio/blob/master/LICENSE) license. > And most important, there is extensive background and details behind the pgsty fork in this pretty informative [blog post](https://vonng.com/en/db/minio-resurrect/). > Commitments > > - No New Features — Just Supply Chain Continuity > - This Is a Production Build, Not an Archive > - I’m willing to Track CVEs and Fix Bugs > - Trademark Is Tricky, But We’ll Cross That Bridge When We Come to It > - AI Changed the Game > Some background: I maintain Pigsty — a batteries-included PostgreSQL distribution with 460+ extensions, cross-built for 14 Linux distros. I also maintain build pipelines for 290 PG extensions, several PG forks, and dozens of Go Projects (Victoria, Prometheus, etc.) packaging across all major platforms. Adding one more [build system] to the pipeline was a piece of cake. > > More importantly, [MinIO is an optional module in Pigsty](https://pigsty.io/docs/minio). Many users run it as the default backup repository for PostgreSQL in production. We did consider several [alternatives](https://vonng.com/en/db/minio-alternative), but none were a drop-in replacement for MinIO-based workflows. > > We use MinIO ourselves, so keeping the supply chain alive was not optional — it had to be done. As early as December 2025, when MinIO announced maintenance mode, I had already built [CVE-patched](https://nvd.nist.gov/vuln/detail/CVE-2025-62506) binaries and switched to them. Finally, as a selfhoster, I also had in mind S3 backend proxies ([Filestash](https://www.filestash.eu/), [SFTPGo](https://sftpgo.com/) etc), but they **consume** S3 or other storage backends and expose web UI apps, or protocols like SMB, WebDAV etc endpoints. Just did a quick search and the other way around also exists: there are API gateways that **expose** S3 API endpoints in front of other backend storage like the local filesystem or virtually arbitrary backends. Not sure this could be interesting, but I'm just apsting below the list of S3 gateway I found crawling a bit: - [rclone serve s3](https://rclone.org/commands/rclone_serve_s3/) that reads 70+ storage backends, - [versitygw](https://github.com/versity/versitygw) for local filesystem, S3-to-S3 proxy etc, - [gaul/s3proxy](https://github.com/gaul/s3proxy) (S3 to Backblaze B2, EMC Atmos, Google Cloud Storage, Microsoft Azure, and OpenStack Swift) - [scality/cloudserver](https://github.com/scality/cloudserver) by zenko, an open-source S3 server over local filesystem or other clouds -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
