Expose S3 endpoint setting via config file
To use non-AWS services like Google Cloud Storage or a custom provider via S3 compatibility, the endpoint needs to be configurable, and separated from the URL to allow Cloudflare etc proxy for SSL termination. eg for GCS in S3 mode with custom domain: AWS_ENDPOINT="https://storage.googleapis.com" AWS_URL="https://i.pitchfork.club" This is already supported via the driver, it just needs a config option to feed it in. https://laracasts.com/discuss/channels/laravel/custom-file-driver-digital-ocean-spaces?page=1
This commit is contained in:
parent
833d17db4e
commit
d483f4a01f
1 changed files with 7 additions and 6 deletions
|
@ -56,12 +56,13 @@ return [
|
|||
],
|
||||
|
||||
's3' => [
|
||||
'driver' => 's3',
|
||||
'key' => env('AWS_ACCESS_KEY_ID'),
|
||||
'secret' => env('AWS_SECRET_ACCESS_KEY'),
|
||||
'region' => env('AWS_DEFAULT_REGION'),
|
||||
'bucket' => env('AWS_BUCKET'),
|
||||
'url' => env('AWS_URL'),
|
||||
'driver' => 's3',
|
||||
'key' => env('AWS_ACCESS_KEY_ID'),
|
||||
'secret' => env('AWS_SECRET_ACCESS_KEY'),
|
||||
'region' => env('AWS_DEFAULT_REGION'),
|
||||
'bucket' => env('AWS_BUCKET'),
|
||||
'url' => env('AWS_URL'),
|
||||
'endpoint' => env('AWS_ENDPOINT'),
|
||||
],
|
||||
|
||||
],
|
||||
|
|
Loading…
Reference in a new issue