Piston

Piston

If you use svn:externals to manage plugins for your rails application then this utility will definitely make your life easier. It allows you to keep a copy of the plugin in your local repository and also allows you to update it with the external source.

What is the benefit of having a local copy of the plugin in your repository versus using svn:external? When you do svn update, it will be a lot faster since it doesn't need to go out to external repositories to check for updates.

When you want to sync the plugin with the external source, all you have to do is type:

$piston update vendor/rails

and then

$svn commit --message "sync up plugins with external source"

Life couldn't be easier.