Our great sponsors
-
Puts Debuggerer
Ruby library for improved puts debugging, automatically displaying bonus useful information such as source line number and source code.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Didn't know that MinIO used to be Apache licensed. This [0] is the commit that changed it.
Since the S3 API largely remained the same over the last two years, it might be an option to use the Apache version, if AGPL is not possible. Of course, that would lack security fixes that were done in the meantime.
There is also a discussion [1] about that license change.
[0]: https://github.com/minio/minio/commit/069432566fcfac1f105367...
[1]: https://github.com/minio/minio/issues/12143
According to commonly understood agpl interpretation you’re correct but not as minio understands it:
> Combining MinIO software as part of a larger software stack triggers your GNU AGPL v3 obligations.
> The method of combining does not matter. When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the larger stack and MinIO.
https://github.com/
Related posts
- Show HN: Live conversations with ChatGPT using WebRTC
- GitHub's User Content certificate has expired
- Nuclear-fusion lab achieves ‘ignition’: what does it mean?
- Using LFS, file tracked, but push rejected with status that I should use LFS to track
- go.mod in a library that is to be imported.. but used in local dev while developing it...