We mirror the plugins we use with svk into the svn repo and then use svn externals into the same repo. This setup has been working without problems for us.
You can lock to specific plugin revisions with the usual -r option in the external On Oct 24, 8:46 pm, Jean-nicolas Jolivet <[EMAIL PROTECTED] s.net> 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? > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
