Closed jlerpscher closed 10 years ago
When using Direct upload with CarrierWave, the library automatically takes the image's details and stores it as the identifier. You can have a look at the Sample project which demonstrates both server-side and client-side uploads, including CarrierWave integration. https://github.com/cloudinary/cloudinary_gem/tree/master/samples/photo_album
Thank you for your answer.
The solution provided in the sample app require javascript. I am looking for a solution without any javascript.
If you want to convert an upload response to something CarrierWave will be willing to accept, you can use:
Cloudinary::Utils.signed_preloaded_image(params)
Hi,
Sorry, back from holidays.
Cloudinary::Utils.signed_preloaded_image(params)
doesn't seems handle private upload, I need something like:
"image/private/v1404760155/aaar1lttbgujqhdaaa.jpg#aaaaaab0b57be13297c6bb0a790e309"
but I get something like that:
"image/upload/v1404760287/cwuqrownwmqxl3pay4de.jpg#8cf120c91bb36a8e8a136170b6a8e28431bcdc18"
"#{result["resource_type"]}/upload/v#{result["version"]}/#{[result["public_id"], result["format"]].reject(&:blank?).join(".")}##{result["signature"]}"
params type it is not used in the function. Am I missing something?
works great! Thank you.
Hi,
I am trying to upload directly to Cloudinary, bypassing my rails app. I am working with Carrierwave and a Picture Uploader .
Until now, everything is fine. But in my controller, I am unable to save the picture path unless doing the following:
I guess it's not the cleanest way to do that.
I have tried to build directly with params but it did not save. I also tried with cloudinary_url but it also failed. The result looks like:
The params are:
So, what is the best way to upload to cloudinary bypassing my rails app?