easy way to use the ActiveRecord connection instead of a separate Sequel one

[senny]

queue_classic is extremely awesome! I think the integration with Rails could be improved though. Most Rails apps use ActiveRecord and last time I checked there is no easy way to share the connection with QC. this would immediately yield the following benefits:

• zero config integration with rails
• share transaction scope (allows to roll-back jobs inserted in a transaction when things go wrong)

I would be willing to work up a PR to make this integration as smooth as possible. What do you think?

[ryansmith3136]

@senny great to see that you are interested in improving the DX here. I think you are right, we can definitely make the integration better. Currently, the QC::Connection module allows the setting of a connections variable. You can get the connection object from ActiveRecord and pass it to QC::Connection. I would love to see what you come up for improving the situation.

To get things started, what would the README look like if we had better rails support. What would the install/setup instruction be for a Rails app?

[senny]

thanks @ryandotsmith for the update. Looks like my arguments were not based on the latest version of QC. I think the current documentation already makes the integration much simpler. What we could do is provide a Railtie to automatically set the connection for you and integrate the rake tasks. Then only the migration needs to be added, which could be provided by a generator. As the current setup looks reasonable I think the manual approach is not that bad.

[senny]

As I see it the README could look something like:

Gemfile

gem 'queue_classic'

To add the necessary migrations you can run the qc:installgenerator.

rails g qc:install

[senny]

I'm closing this one in favor of #134