Using Cloudinary for a gallery project
After working with Imagevuex.com for several years, we are now planning next generation portfolio gallery, and after reviewing Cloudinary, it is obvious we need to offer this service as an option in addition to self-hosting and various other picasa/flickr. It is likely we will in fact recommend our customers to choose Cloudinary, as the advantages are undebatable.
Working on some logics however, I am trying to figure the best way to work with Cloudinary in regards to categories (or folders) in a gallery website. One way would of course be to keep track of remote images for a specific category from within the websites own system(DB), but it seems there may be an easier and more flexible way ... We could add category/ID as a tag when uploading the images to cloudinary, and then list images by tag when calling them for a specific category later.
Did I miss any concept logic? Thanks, Cloudinary looks great!
-
Hi Karl,
You can either use tags, folders or prefix. However, Cloudinary's advanced listing (list by tags, prefix, etc.) is only available as part of Cloudinary's admin API that is intended to be used from the server-side, not client-side.
Supporting full DB-like capabilities that are safe to use from the client-side is in our road-map. In the meanwhile, in this case, the solution should be based on an internal DB.
0 -
Thanks for the reply. Is there any reason why the Cloudinary "admin api" can't be used by our backend PHP to feed the frontend? I don't see why these benefits like getting images by tags should be limited to some backend admin api ... It is clearly a benefit for listing images in a frontend interface also.
Why would we prefer to not use our own internal database? We produce and distribute image gallery websites, and database is simply another level of complexity, slowness and inconvenience that provides no advantage in a day and age that many modern websites are looking away from DBs (eg getkirby.com, statamic.com). As example, we offer several ways to for displaying photos in a gallery:
- Self-hosted - Files can simply be listed from within a folder. *No need for DB
- Flickr/Picasa - Files can simply be listed by making a call to a specific category ID in their API. *No need for DB
- Cloudinary - Super cool both for us and our customers, but not possible to integrate without relating all images to "pages" from within an internal DB.
Seems inconvenient that it would not be possible to avoid DB with cloudinary considering everything else it could do. Would it not be helpful to extend the scope and perhaps use a "category", and then also consider an API function that is not "admin api" which allows listing images from a tag or category? Please consider it a request! ;)
If something like this was in place, it would be the perfect accompaniment for portfolio websites. We would have to recommend it to all our clients as a superior option with no cons, and Im sure plenty would be upgrading to one of the premium services. Thanks!
0 -
Hi Karl,
Thank you for your suggestion.
Adding client-side image listing by tag API is on our road-map, we'll be happy to let you know once it's available.0 -
Any updates on availability of this feature?
0 -
While client-side image listing by tag API is still on our road-map, we don't have an ETA for this yet.
0
Post is closed for comments.
Comments
5 comments