optionally can define endpoint URL

[schneidermr]

With my changes, the S3 module will be able to support other storage with S3 compatible API's

Fixes: #28

[schneidermr]

I'll check and fix that linter error, but the unit test error looks a bit strange to me. It seems like it's failing to another adapter

[schneidermr]

@stnguyen90 Please confirm my suspicions, but as I see these lint problems are not related to my changes

[stnguyen90]

unit test error looks a bit strange to me. It seems like it's failing to another adapter

Yes, you can ignore that failing unit test

these lint problems are not related to my changes

The lint problems might be related as it mentions the S3.php file and you modified that file. You can easily fix the lint problems by running the formatter (composer format).

[stnguyen90]

@schneidermr, were you able to test this adapter with a couple of different providers to make sure it works? Can you provide some screenshots of successful tests?

[schneidermr]

@schneidermr, were you able to test this adapter with a couple of different providers to make sure it works? Can you provide some screenshots of successful tests?

I've to find some free providers for the test because I'm using GCP, but until that here is the demo with Cloudflare R2.

r2.mp4

[eldadfux]

PR looks good, but we need tests to pass before we can merge.

[schneidermr]

PR looks good, but we need tests to pass before we can merge.

The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential.

storage/tests/Storage/Device/LocalTest.php

Line 258 in 5af2bd0

$key = $_SERVER['S3_ACCESS_KEY'] ?? '';

@eldadfux it seems the problem is not in the code.

[pietrodicaprio]

Checking the latest open PRs: it looks like they are all failing the unit tests due to the empty variable.

Are the secrets properly set in the repo and readable by the Action executed on a PR from a non-member?
The latest passing is #105 but the committer is a Contributor.

The secrets are not readable from actions run on pull_request. It's required to set pull_request_target as trigger. Here an example of a repo I own: https://github.com/Vanilla-OS/ABRoot/blob/main/.github/workflows/go-pr.yml#L4C23-L4C23

GitHub doc reference: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflows-in-forked-repositories and https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target

[pietrodicaprio]

Nice workaround @lohanidamodar , I hope you don't plan to do this for every PR 😆