On Wed, Jul 8, 2009 at 5:25 PM, Colin Law<[email protected]> wrote: > > 2009/7/8 Pål Bergström <[email protected]>: >> >> I use rails 2.3.2. The server use 2.1.1. What do I do? Make a new app on >> my side based on 2.1.1? If yes, how do I do that? >> -- >> > > The best plan would be to get the server updated if possible.
Another options is to put rails 2.3.2 into the app structure itself: On the development machine rake rails:freeze:gems This puts unpacks the gems which comprise rails ( activerecord, activesupport, actionpack etc) under the vendor/rails Assuming that deployment is via a repository (svn, git...) commit the application making sure that vendor/rails is placed under version control. Then it doesn't matter what the current 'official' rails version is on the server, it will use the same version you use in development. This is a bonus both ways, you can use a later version than the one installed as gems on the server, and you are isolated if the 'it guys' update the rails gems without telling you, something which can easily break your app. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
