Skip to content

Conversation

@tonypiper
Copy link
Contributor

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.

tonypiper and others added 2 commits December 16, 2024 11:28
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.
Copilot AI review requested due to automatic review settings September 23, 2025 17:41
@duncanmcclean duncanmcclean merged commit 94e8fdd into statamic:5.x Sep 23, 2025
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR improves the documentation for configuring Glide image manipulation with CDN caching by addressing a common configuration pitfall. The changes clarify that separate buckets and URLs should be used for Glide cached images versus source assets.

  • Updates configuration example to use distinct environment variables for Glide bucket and URL
  • Enhances warning message to explicitly mention URL separation requirement

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

duncanmcclean added a commit that referenced this pull request Sep 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants