Well my immediate problem is that I'm trying to upgrade from hoptoad
v1 to hoptoad v2 and running into enormous problems. Right now since
I'm working with their tech support I need to do what they recommend
and it isn't Bundler. I will definitely investigate it for other
things in the future, though.
By the way, do you know how to "un-vendor" a gem? Can I just do
something like:
rm -rf /vendor/gems/hoptoad_notifier-2.1.2
Or should I do something else?
Thanks, Ken
On Jan 28, 2010, at 8:09 AM, Martin Emde wrote:
You can specify a version with confug.gem and that will keep it from
updating later. I still say you should use bundler. The problem with
rake gems:install is that you usually need to have the gems installed
already to run the rake task. Yes... It's as stupid as it sounds.
Bundler just has you type "gem bundle" which will always consistently
package the same gems (if you specify versions) into vendor/gems/ and
will isolate the app from the system environment (also if you specify,
which you should).
Martin
/ on my iPhone
On Jan 27, 2010, at 16:33, Brandon Black <[email protected]>
wrote:
As a separate, but somewhat related note...
You guys should check out the dependencies gem that is used by Monk.
It presents a pretty good alternative to managing all your gems in
the
traditional way. Monk is primarily for Sinatra based web applications
rather than a rails application, but you could probably create a
rails
project skeleton if you wanted too and the dependencies gem makes
deploying your app with all its necessary gems extremely clean and
easy.
Dependencies Gem
http://github.com/djanowski/dependencies
Monk
http://www.monkrb.com
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
http://www.nealstreetdesign.com
http://www.shareastronomy.com
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
