Comments on: Keeping Up With The Joneses: Keeping Rails and its extensions up to date

By: Chris Kottom

Chris Kottom — Mon, 06 Apr 2009 05:02:01 +0000

Re: setting up project using Edge Rails. Why not simply create the project using whatever version of Rails you have installed, and then use the appropriate Rake tasks to freeze the project to Edge Rails (rails:freeze:edge) and then update the project to conform to whatever version you just installed (rails:update). If I understand the usage of these correctly, this should give you the desired effect without nearly as many manual steps.

By: vipul

vipul — Fri, 20 Mar 2009 15:51:55 +0000

gem install pluginname

works for me. but

scipt/plugin install git://………….

does not work for me . Can you tell me the reason?

I’m on rails 2.2.2, ruby 1.8.7 and gem 1.2.0

it gives me this error: vipul@vipul-laptop:/$ script/plugin install git://github.com/activescaffold/active_scaffold.git -r rails-2.2.2
bash: script/plugin: No such file or directory

By: Noel Rappin

Noel Rappin — Thu, 19 Mar 2009 18:19:30 +0000

@ben — yes, that’s probably a good idea, although wouldn’t that preclude unpacking the test gems? But it would simplify deployment a little.

@ant — I tried Braid a while back, but found the experience unsatisfying. I wasn’t tremendously comfortable with Git at the time, which probably didn’t help.

By: Noel Rappin

Noel Rappin — Tue, 10 Mar 2009 21:54:50 +0000

@Evgeny — Git submodules may work splendidly. I’ve never quite gotten them to do what I want, and I worry that I won’t be able to recreate a precise moment back in time. But the update process itself seems simpler.

@cs — Engines are just plugins that have their own app directory and share a load path with the main app. They’d be updated like plugins.

By: Ant Ramm

Ant Ramm — Tue, 10 Mar 2009 16:41:48 +0000

How about using Braid: http://github.com/evilchelu/braid/tree/master This allows you to keep track of external vendor branches (either SVN or Git) in your project’s Git own repository.

You can configure it to follow a particular branch, tag or just follow master. All you need to do to update your vendor branches is:
braid update
Easy!

By: Ben Pickles

Ben Pickles — Tue, 10 Mar 2009 09:56:15 +0000

i would suggest using config.gem in environments/test.rb for that mass of testing gems

By: cs

cs — Mon, 09 Mar 2009 22:37:30 +0000

Thanks for the gem/plugin comparision, it’s more understandable now.
What about engines? Currently many solutions come as an engine …

By: Ennuyer.net » Blog Archive » 2009-03-09- Today’s Ruby/Rails Reading II

Ennuyer.net » Blog Archive » 2009-03-09- Today’s Ruby/Rails Reading II — Mon, 09 Mar 2009 15:09:28 +0000

[...] Ruby on Rails » Keeping Up With The Joneses: Keeping Rails and its extensions up to date » Pathfi… [...]

By: Evgeny

Evgeny — Sun, 08 Mar 2009 10:38:46 +0000

All these things to do just to keep up to date, reminds me of pulling teeth. It hurts.

I just manage everything in git with git submodules, vendor/plugins/ are all git submodules, vendor/gems/ are all git submodules, and vendor/rails is a git submodule. Then with much less teeth pulling I can keep up to date with just one or two git commands. And switching to a different version (branch/tag) of a plugin/gem/rails (even when I am offline) is quite easily done.

I’d love to see rails stop doing the teeth pulling already. It hurts. Really.