It should be easier to use Cloudinary as a storage option for ActiveStorage #1617
Comments
jagthedrummer
added a commit
that referenced
this issue
Nov 1, 2024
This makes it easier to use Cloudindary as the backend service for ActiveStorage. From a functional perspective this works very much like the S3 service option. ActiveStorage is still in control of files, but it sends them through to Cloudinary for storage and delivery. Partial fix for : #1617
jagthedrummer
added a commit
that referenced
this issue
Nov 14, 2024
This makes it easier to use Cloudindary as the backend service for ActiveStorage. From a functional perspective this works very much like the S3 service option. ActiveStorage is still in control of files, but it sends them through to Cloudinary for storage and delivery. Partial fix for : #1617
jagthedrummer
added a commit
that referenced
this issue
Nov 14, 2024
#1739) * Make it easier to use Cloudinary as a storage option for ActiveStorage This makes it easier to use Cloudindary as the backend service for ActiveStorage. From a functional perspective this works very much like the S3 service option. ActiveStorage is still in control of files, but it sends them through to Cloudinary for storage and delivery. **NOTE:** If, in production, you use Cloudinary for anything and have a `CLOUDINARY_URL` ENV var set but you want to use the `:local` option for ActiveStorage then you'll want to make an adjustment to `config/environments/production.rb`. Partial fix for : #1617
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we use the presence of
CLOUDINARY_URLto determine whether images should use ActiveStorage or the Cloudinary JS widget for uploads. In a vanilla Rails app it's possible to setup Cloudinary to be the back end storage option for ActiveStorage. One reason you might want to do this is that provisioning the Cloudinary add-on is easier than provisioning an S3 bucket and getting all of the settings just right (IAM, CORS, etc...).We probably need a more explicit trigger so that a developer could have
CLOUDINARY_URLset but still opt in to the ActiveStorage style image handling with Cloudinary as the storage location.Ideally if we can make this work it would:
cl_image_tagandcloudinary_url) instead of relying on ActiveStorage representationsThe text was updated successfully, but these errors were encountered: