This draft includes previously unpublished versions of Chapter 10, "User microposts", and Chapter 11, "Following users". The original announcement is here:
This is a full draft, but it's not yet complete. In particular, I'm considering replacing Blueprint CSS with Bootstrap for the final version. Please let me know what you think.
I agree with everyone else on using bootstrap. Besides becoming the norm there are a couple of steps using available gems that could make a beginner have an easier time setting it up. It could be a difference maker with someone's time.
Also, huge fan of this tutorial. It got me started with Rails a year ago. Best resource I used to learn rails.
Hello, I also started rails by reading your tutorial. I have a question, this post http://stackoverflow.com/a/5612941 suggests that the way to model a friendship is to duplicate rows in a transaction and it cites a book you wrote.
Is this still the way to go? I like the idea of duplicating rows because it simplifies the associations a lot, but I've been warned against it. Is that the way you would do it?
Completely agree, though LESS is nice, I think it would be best for people to be kept within rails "standards" (for want of a better term) which at the moment means SASS. There's also the whole "having to maintain a JS stack" that less necessitates as well, which would be better to leave well alone for beginners I think.
I went the less port because it was being upgraded quicker with the 2.0 release. I've used both and they are both great gems. Both function pretty similar so don't be afraid of the LESS version, its still supported in the assets pipeline!
Well, this tutorial already weighs in at more than 500 pages. That's pretty in-depth if you ask me. :-) But producing more advanced content in the future is definitely a possibility.
I've been learning Rails from your tutorial (just finished Chapter 11), but realised a few days ago that I've been using the 3.0 version. It'd be great to see an appendix on "Transitioning to 3.2 for first edition readers" (probably like the one you've got for 3.0 -> 3.1, but I haven't got to reading that yet.)
And while I'm here, there is a bug in the 3.0 edition in section 11.3.4, listing 11.39. The link_to "delete" needs to reference 'feed_item', not 'micropost'. That took me a good half an hour to sort out - mainly because I assumed it was my fault, not yours! :-)
Thanks for all your efforts here; this is a fantastic resource.
Oops, you're right. That's actually a new bug, and has now been fixed.
As far as the transition goes, that's a great candidate for a blog post, but it's not as good a fit for a book. Plus, experience shows that starting from scratch often takes less time in the end.
Fair enough. My current plan when I've finished is to rewrite my collaborative blogging platform in Ruby (was Google App Engine + Python). It's got enough similarities to a twitter clone that I can base a lot of the infrastructure on railstutorial, but enough differences that I will definitely start from scratch rather than trying to modify the codebase. I guess I should move to rails 3.2 at the same time, and whizz through your new version in parallel.
Not sure if you are aware of this...for the first edition of your tutorial, webrat is required for many of the tests (I tested on ubuntu/windows), but inclusion of webrat will actually break some of the new tests (like those using have_selector) in the second edition. You might want to add a warning to those who have followed the first edition and are trying to incorporate the additions in the second edition.
It would be nice if you can discuss the differences, like how Capybara is meant for integration tests, and replacement for have_template etc. At some sections the tests are still referred to controller tests (Listing 10.46) although it looks like you intend to convert them all to integration tests.
Is there a change log or something of the sort? I am actually half way through chapter 4 and looking back I see some differences between what I've already done and what is presented on the site, just want to make sure I'm either not missing things or what I've already written is ok to continue with.
This tutorial was my first exposure to Ruby and Rails. It is amazingly comprehensive and comprehendible for newbies. I'm so glad to see it being regularly updated.
Rails Tutorial was my first step in developing. It was extremely helpful and I used both the book and screen casts which helped me alot. For a complete newb it was a bit overwhelming but I was still able to follow along and eventually get the sample app live. Now I am trying to learn more pure ruby and going back through the tutorial and learning even more. Thanks again Michael this has been by far the best resource I have used so far.
So far really liking the tutorial. Just one thing, as a rails newbie, could you expand a little more on the deploying part of section 1, specifically giving an example of deploying NOT using heroku.
It's just I want to be deploying to just a generic server running rails and I want to know how the process is different. I know you have to set the ENV to production but at what stage of the process does this happen etc...
I second that. Capistrano does have a very comprehensive run down of how that all works but for the beginner I can see them getting lost with those. Most Rails tutorials I've seen either tell you to deploy to Heroku or if they don't they don't cover deployment to your own server so much, it usually feels like a quick skim.
http://news.railstutorial.org/a-full-draft-of-the-ruby-on-ra...
This is a full draft, but it's not yet complete. In particular, I'm considering replacing Blueprint CSS with Bootstrap for the final version. Please let me know what you think.