On Oct 24, 2007, at 11:46 AM, Jean-nicolas Jolivet wrote:
> > Just a simple deployment question.... would it be a better idea to > include the plugins I install in my project's SVN repository? Or > should > I ditch them and re-install them in my production environment? > > Personally I thought it might be a better idea to include them in my > project SVN so that way I'm sure that the same version of the plugin > will be used once I deploy my app in production environment... Any > reasons why I shouldn't do it? > > Also, besides the database config file and temp directories (tmp, > cache, > logs etc)... anything else I should EXCLUDE from my projet's svn repo? > In my opinion, yes. Lock everything to versions that you've tested with. This is where Piston comes into play. We import plugins into our svn via piston so that we aren't relying on svn external repositories to stay up/active... or heaven forbid they make changes and it breaks our application on our next deployment. Here is an article that I wrote on using Piston. * http://rubyurl.com/qZi Hope that helps! Cheers, Robby -- Robby Russell Founder and Executive Director PLANET ARGON, LLC Design, Development, and Hosting with Ruby on Rails http://www.planetargon.com/ http://www.robbyonrails.com/ +1 503 445 2457 +1 877 55 ARGON [toll free] +1 815 642 4068 [fax] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
