On 10/24/07, Robby Russell <[EMAIL PROTECTED]> wrote: > > > 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
Same goes for rubygems, (frozen with my gems plugin, http://svn.techno-weenie.net/projects/plugins/gems/), or even edge rails. I have a rake task that exports specific edge rails revisions and creates symlinks for all deployments. Mike Clark had an excellent blog post taking you from using svn:externals for rails (icky) to using the 'cadillac style' of freezing rails (adapted from some of my rake tasks). One nice thing is you can easily roll back if things break, rather than jump into your server(s) and rollback gems manually. Here's one example of the rake task, it's been used in all my rails deployments: http://svn.techno-weenie.net/projects/mephisto/tags/rel-0.7.3/lib/tasks/common.rake -- Rick Olson http://lighthouseapp.com http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
