dragonfly-activerecord

Provides a data store for Dragonfly, backed by ActiveRecord.

Requires a Rails application using Dragonfly 1.0+.

Tested with MRI 1.9.3, 2.0, 2.1; ActiveRecord 3.2 and 4.0; and MySQL, PostgreSQL, and SQLite stores.

If your app's dynamic assets (user uploaded images for instance) weigh up to a few gigabytes, it can make sense to store them in the app's database instead of another service (e.g. Amazon's S3): your stack has one less dependency to care about, and backups get more complicated.

dragonfly-activerecord, lets you store assets to your app's relational database.

Add this line to your application's Gemfile:

gem 'dragonfly-activerecord'

Create a migration:

$ rails generate migration add_dragonfly_storage

Edit the migration file:

require 'dragonfly-activerecord/migration'

class AddDragonflyStorage < ActiveRecord::Migration
  include Dragonfly::ActiveRecord::Migration
end

Run the migration:

$ rake db:migrate

Configure Dragonfly itself (in config/initializers/dragonfly.rb, typically):

require 'dragonfly-activerecord/store'

Dragonfly.app.configure do
  # ... your existing configuration here
  datastore Dragonfly::ActiveRecord::Store.new

... and you're good to go!

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