2.0?

I’ve havn’t run across a brief synopsis via search so I thought I’d
throw the question out here.

As my first real application is still a work in progress I suppose I
should upgrade to 2.0 before I finish it off. (especially as I’ve just
seen a couple good tutorial on implementing restful authentication in a
2.0 enviornment and would prefer to follow them lock-step)

Are a lot of things going to stop working? (Im not using any
scaffolding).

How will I get the new features like initializers into my existing
projects?

Do I need to rename things with rhtml extensions .html.erb ?

Will I need to change the format of my migrations to the new way?

Would it be a good idea just to scrap the existing application and cut
and paste code after regenerating controllers and models? (sounds like
a lot of work!)

Are a lot of things going to stop working? (Im not using any
scaffolding).

Depends on what you’re using. Classic Pagination and Scaffolding are the
two
main things people are having issues with at the moment.

Do I need to rename things with rhtml extensions .html.erb ?

It would be wise, but is not neccessary.

Will I need to change the format of my migrations to the new way?

No, all migrations still support the old syntax as well.

Would it be a good idea just to scrap the existing application and cut
and paste code after regenerating controllers and models? (sounds like
a lot of work!)

No, it would be very time consuming. It’s best just to work through
whatever
errors you get.


Posted via http://www.ruby-forum.com/.


Ryan B.

Feel free to add me to MSN and/or GTalk as this email.

Thanks for the quick replies Ryan but I missed the answer on how I get
the new features like initializers into an existing application.

I poked around on the rails.org site and found the directions I hope
will work. I’m sorta wary about doing it but I guess I’ll take the
leap.

http://wiki.rubyonrails.com/rails/pages/HowtoUpgrade

*  gem update rails -y

or

* sudo gem update rails -y


*  Open your_project/config/environment.rb and change 

RAILS_GEM_VERSION to point to the version you just upgraded to
* Run rake rails:update from your project’s root directory
* Verify that any tests you may have written still pass

Hi Tom,

I updated our rails app to 2.0 in December and apart from fixing
deprecated issues and patching some third party gems there wasn’t much
to do. To get initializers to work, all I had to do was to create and
initializers directory under config and drop in my .rb file. To be
fair, we don’t use the features that Ryan mentions but I can’t say
that we’ve had much other than a smooth transition from 1.x to 2.x.

Chris

On Jan 9, 11:00 pm, Tom N. [email protected]

What specifically about initalizers do you need?

On Jan 10, 2008 9:30 AM, Tom N. [email protected]
wrote:

  • gem update rails -y


Posted via http://www.ruby-forum.com/.


Ryan B.

Feel free to add me to MSN and/or GTalk as this email.

There are a few things that will break. If you are using scaffolding
of any sort, you’ll have to do some work. If you’re using Rails
pagination, you’ll have to decide on Rails classic_pagination or
will_paginate. I posted a blog entry on some of this stuff:

http://calicowebdev.com/blog/show/17

I upgraded an app that was pre-REST to 2.0 and made it RESTful in
about a day. YMMV.

:slight_smile:

Which tutorials did you see?

On Jan 9, 12:30 pm, Tom N. [email protected]