From 82fe9e1c98f2a0ed65b9c94b59cdf4664c9fc091 Mon Sep 17 00:00:00 2001 From: Tony Piper Date: Mon, 16 Dec 2024 11:28:41 +0000 Subject: [PATCH] Update image-manipulation.md fix a papercut when configuring glide to use a CDN cache - despite the warning on line 214, I managed to overlook specifying a distinct url and couldn't figure out why the asset browser wasn't working. It was because I had AWS_URL pointing to the Glide bucket, not the assets bucket. Hope this helps someone else. --- content/collections/docs/image-manipulation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/collections/docs/image-manipulation.md b/content/collections/docs/image-manipulation.md index d7aae8642..cf11fd8d9 100644 --- a/content/collections/docs/image-manipulation.md +++ b/content/collections/docs/image-manipulation.md @@ -198,8 +198,8 @@ You may choose to save your cached Glide images to somewhere CDN based, like Ama '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'), // [tl! **] + 'bucket' => env('AWS_BUCKET_GLIDE'), // [tl! **] + 'url' => env('AWS_URL_GLIDE'), // [tl! **] 'endpoint' => env('AWS_ENDPOINT'), 'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', false), 'visibility' => 'public', // [tl! **] @@ -212,7 +212,7 @@ Make sure that the `visibility` is `public` and that the `url` points to the cor ::: :::warning -Don't use the same disk or bucket as your source images. If you were you to clear your Glide cache (e.g. when using the `glide:clear` command) the whole disk will be emptied. +Don't use the same disk, bucket or url as your source images. If you were you to clear your Glide cache (e.g. when using the `glide:clear` command) the whole disk will be emptied. ::: ## Path Cache Store