فهرست منبع

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
Mike Barnes 6 سال پیش
والد
کامیت
d483f4a01f
1فایلهای تغییر یافته به همراه7 افزوده شده و 6 حذف شده
  1. 7 6
      config/filesystems.php

+ 7 - 6
config/filesystems.php

@@ -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'),
         ],
 
     ],