What needs to be done to update a rails app after I''ve updated rails? I''ve copied the new javascript files, but I want to make sure I don''t miss anything. Thanks. -- Jack Christensen jackc-/SOt/BrQZzOj3I+7jmQ39gC/G2K4zDHf@public.gmane.org
Jack Christensen wrote:> What needs to be done to update a rails app after I''ve updated rails? > I''ve copied the new javascript files, but I want to make sure I don''t > miss anything. > > Thanks. >If you are using version control, it''s very easy to run ''rails myapp'' over the top of your existing app and then inspect exactly which files change. Any files that you''ve edited manually can then be rolled back or merged as necessary. Any new files (e.g. dispatch.*, *.js) can be committed. This is ripped straight from the rails 0.13 announcement [1]. "Fully backwards compatible! As has been the norm since around 0.9.0, this release is mindful of backward compatibility, so despite the flow of fixes, improvements, and features, your existing applications won’t need to be updated code-wise. All you need to do to upgrade is get the new gems with gem update rails and then generating the new infrastructure files with rails <your-app-dir>. You want to overwrite the dispatches, the prototype library, the Rakefile, and the test_helper.rb. Don’t overwrite application_controller.rb, application_helper.rb, or other files you may have tailored, though. It’s always good to do this run on a backup first and check that every things work." [1] http://weblog.rubyonrails.com/archives/2005/07/06/rails-0-13-225-features-fixes-in-75-days
On 7/19/05, Jack Christensen <jackc-/SOt/BrQZzMOf2zXYvRtkodd74u8MsAO@public.gmane.org> wrote:> What needs to be done to update a rails app after I''ve updated rails? > I''ve copied the new javascript files, but I want to make sure I don''t > miss anything.All you need to do is re-run the rails command against the current directory, ''rails .'' answering no to any files which you may have modified.
In article <c18843c60507191041170a0c1b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>, joshknowles- Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org says...> All you need to do is re-run the rails command against the current > directory, ''rails .'' answering no to any files which you may have > modified.Is there any thought to rails providing some simple assistance to this - say, letting me say "yes" to any of those files that haven''t been modified since installation? -- Jay Levitt | Wellesley, MA | I feel calm. I feel ready. I can only Faster: jay at jay dot fm | conclude that''s because I don''t have a http://www.jay.fm | full grasp of the situation. - Mark Adler
>>> All you need to do is re-run the rails command against the current >>> directory, ''rails .'' answering no to any files which you may have >>> modified. > > Is there any thought to rails providing some simple assistance to this - > say, letting me say "yes" to any of those files that haven''t been > modified since installation?If you do a "rails myapp", you''ll be asked if you want to replace or ignore each file in turn. In general, there are only a few that you might have changed. Really, though, this situation is exactly what version control and diffing programs are meant for. It seems inappropriate to add this ability to Rails itself.