"Rails Subversion External Management with Piston" by flinn

Sun, 4 Feb 2007 00:25:00 EST

I’ve been mulling over the best way to manage the many plugins I use that have external svn repositories. Luckily Piston makes light work of vendor branch management in rails.

Piston Homepage

Here’s a rundown:


$ gem install --include-dependencies piston

$ cd $your_rails_project_cwd

$ piston convert
Importing 'http://svn.techno-weenie.net/projects/plugins/acts_as_versioned' to vendor/plugins/acts_as_versioned (-r 2691)
Exported r2691 from 'http://svn.techno-weenie.net/projects/plugins/acts_as_versioned' to 'vendor/plugins/acts_as_versioned'

...

$ svn proplist --verbose vendor/plugins/acts_as_versioned/
Properties on 'vendor/plugins/acts_as_versioned':
  piston:root : http://svn.techno-weenie.net/projects/plugins/acts_as_versioned
  piston:local-revision : 19
  piston:uuid : 567b1171-46fb-0310-a4c9-b4bef9110e78
  piston:remote-revision : 2691

Now, when I deploy my app with capistrano or check out a cwd with subversion I’ll grab revision 2691 of acts_as_versioned instead of a newer revision that I haven’t tested with my app.

Ok, great I could have done something similar by hand, but Piston makes handling the large number of plugins very easy to deal with super easy to manage updates.

Problem Solved. Thank you Piston developer François Beausoleil!

Right Traq Blog comments on Rails Subversion External Management with Piston

"Rails Subversion External Management with Piston" by flinn