No commit activity in last 3 years
No release in over 3 years
Cloudinary based data store for Dragonfly. Works with the latest read write destory interface.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

>= 1.3.0, ~> 1.3
>= 1.0, ~> 1.0
 Project Readme

Introduction

Dragonfly is great for on the fly image processing in your Ruby or Rails application. Being an awesomely extensible software, dragonfly has a very clean and simple API for implemeting custom data stores. There are data stores for Dragonfly that write to S3, MongoDB and CouchDB. There is an old project that provides a cloudinary based datastore for dragonfly. But that project is not actively maintained and it doesn't work with the latest dragonfly interface for read, write and destory.

So I created this gem which supports the latest dragonfly interface.

Usage

If using Cloudinary on Heroku, the config is read automatically from CLOUDINARY_URL environment variable. Else, just download your cloudinary.yml file and place it in your config directory.

Then in your dragonfly initializer, declare cloudinary as the data store with the following line.

app.datastore = Dragonfly::CloudinaryDatastore.new

With PushType CMS

PushType is a cool CMS for rails. If you want to use cloudinary for storing media in your PushType based application, read ahead. You will specially need it if you want to run your PushType application on Heroku.

In the config/initializers/push_type.rb file, comment the line that configures :file datastore and add the line config.dragonfly_datastore = Dragonfly::CloudinaryDatastore.new

TODO

  1. Add some tests

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request