How to use an ActiveRecord plugin in a non-Rails project

Rails
1

I’m using ActiveRecord on a Sinatra app. I need one of my tables to be
sorted, so I’m using acts_as_list
(GitHub - brendon/acts_as_list: An ActiveRecord plugin for managing lists.).
However, it isn’t a gem, so I don’t know how to get it to work with
Bundler.

Currently, I just cloned the source into a dir named “vendor”. This
works,
but when I search my code, it keeps including acts_as_list code in the
results. It also means more folders and files, so just generally more
overhead. I’d like it to be as transparent as all the gems I use.

Is there some way to get Bundler to deal with it, or is there a best
practice for this situation?

(I was thinking I could probably fork it, give it a gemspec, and then
tell
Bundler to look at my forked repo, does that sound reasonable?)

2

On Sat, May 28, 2011 at 7:32 AM, Josh C. [email protected]
wrote:

I was thinking I could probably fork it, give it a gemspec, and then tell
Bundler to look at my forked repo, does that sound reasonable?

I ended up doing this. GitHub - JoshCheek/acts_as_list: This repo is no longer necessary as the real gem has incorporated these ideas. Add one
fairly simple file, and now it works with Bundler. Then load it into my
app
with:

require “active_record/acts/list.rb”
ActiveRecord::Base.send :include, ActiveRecord::Acts::List

I think this was a good solution.

3

Hey Josh,

Just as a side note, I think it would be more respectful to list all the
authors of this gem in your gemspec file

Gem::Specification.new do |s|
…
s.authors = [‘Joshua Cheek’]
…
end

Wael