Officially support minio as a provider

EWhite613 commented 3 months ago

In this PR:

Support MINIO as storage provider. Can just use s3 and s3ForcePathStyle: true and it'll work
- fixes #149 in official manner (solutions already provided in comments on that issue)
  Issues reference:
- https://github.com/ducktors/turborepo-remote-cache/issues/149

x ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you lint your code with pnpm lint locally prior to submission?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
- Any ideas on writing a good test? The s3 tests do s3ForcePathStyle for the s3 tests, and that's all Minio support requires in addition to s3. I could just copy the s3 tests and change the provider but it's gonna have the same output for that
[x] Have you successfully ran build with pnpm build of your changes locally?
[x] Have you successfully ran tests with pnpm test of your changes locally?
[x] Have you commit using Conventional Commits?

matteovivona commented 3 months ago

@all-contributors add @EWhite613 on code

allcontributors[bot] commented 3 months ago

@matteovivona

I've put up a pull request to add @EWhite613! :tada:

matteovivona commented 3 months ago

:tada: This PR is included in version 2.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: