To answer a previous question, that being, "why do you have to restart the server after editing the routes", the reason is because the file config/routes.rb is read when the server loads, and its information stored in memory. The application doesn't want to re-load the routes file for every request because it just adds overhead, making it take more time (we're talking fractions of a second, but that adds up significantly over several thousand users) to process a request.
As far as your point of taking advantage of all the cool new stuff, just to let you know, Rails v. 2.x is basically outdated now. Rails 3.0 was released just a few weeks ago (prior version was 2.3.9) and has a LOT of new stuff - relationships are different (see "Arel" or "ActiveRelation" - same thing), the database agnosticism has different ways for doing queries (see "ActiveRecord" version 3), routing is very different (config/routes.rb as above), and so on. Given that you're just starting out, you can install the 2.x series of Rails as you have above and get along fine - it'll make a lot more sense as you're moving along with the book. But just remember that the latest and greatest is already a full version release ahead of the book. This is one major reason I usually don't bother buying books on anything related to Ruby - the community moves way too fast for a book to be relevant, and usually breaks - quite unabashedly - backwards compatibility in doing so. This isn't so much a criticism as an observation, by the way. Also, to the points about Subversion above - all the points apply to most modern source control systems and aren't unique to Subversion. SVN is pretty awesome and I've been a fan of it for years (so this is in no way meant as a "slam" to the original author for mentioning it, only an elaboration on it), but the "cool kids club" these days seems to prefer a tool called "git". The Ruby community seems to be very "populist"/teen-girl in its behavior on what tools are considered "best of breed" at any given moment. I swear to God it reminds me of junior high - when brand X was popular but you were considered a leper if you used brand Y. Rewind to 2006 or so and Subversion was all the rage. Today it's git. Three years from now, who knows. I don't buy the whole "git > svn > perforce > cvs" etc. arguments as a whole unto themselves - you just need to understand that there are different tools that work better or worse than another in a given situation (that being, your workflow), and there are other constraints to consider in the reality of a multi-user, usually corporate or somewhat- mature start-up like environment, where you can't go dicking with server configs and all the "new shiny" stuff three times a day - you eventually have to actually get work done, too. Just thought I'd elaborate on those points to give you some more information on the general direction of things :) Linkage incoming: Git: http://git-scm.org/ Subversion: http://subversion.apache.org/ Rails Guides - an excellent supplement to the book: http://guides.rubyonrails.org/ Good luck man! On Oct 12, 11:17 pm, "Wyatt R." <[email protected]> wrote: > > If using Rails 3.0 then before restarting server with "rails server" > > edit "config/routes.rb", and uncomment the following line: > > > match ':controller(/:action(/:id(.:format)))' > > > then restart server > > THIS WAS AMAZING. THANK YOU SO MUCH. > > Why does no one say anything about this anywhere else?! Thanks neels! > > -- > Posted viahttp://www.ruby-forum.com/. -- 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.
