# Upgrading an old rails project to the newest version

**URL:** <https://www.ruby-forum.com/t/upgrading-an-old-rails-project-to-the-newest-version/109176>\
**Category:** Rails\
**Created:** [July 12, 2007, 5:41am UTC](https://www.ruby-forum.com/t/upgrading-an-old-rails-project-to-the-newest-version/109176 "2007-07-12T05:41:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\
**Post date:** [July 12, 2007, 5:41am UTC](https://www.ruby-forum.com/t/upgrading-an-old-rails-project-to-the-newest-version/109176/1 "2007-07-12T05:41:13Z")

</div>

Does anybody have any tips on upgrading an older rails project to a  
newer version of rails? I have a project that is still calling up  
WeBrick in dev mode and I’d like to bring it up to date. Short of  
creating a whole new rails project and copy-pasting, is there a quick  
and easy way to upgrade?

Thanks!

---

<div class="post-metadata">

**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\
**Post date:** [July 12, 2007, 7:11am UTC](https://www.ruby-forum.com/t/upgrading-an-old-rails-project-to-the-newest-version/109176/2 "2007-07-12T07:11:20Z")

</div>

First commit anything you’ve done and tag it with some note about the  
working version of Rails that supports that code. Next:

rake rails:freeze:edge  
(if it’s really old, then just rake freeze edge)  
rake rails:freeze:edge

Yes, I really meant to type that twice. The first time you update  
most of the core but don’t pull down ActiveResource, the next time,  
the new Rake task is on your local computer so ActiveResource is added.

Then

rake rails:update

rake

And see what tests are broken.