41–48 of 48 posts
Earlier quoted context omitted.
Which SASS port do you prefer ? https://github.com/thomas-mcdonald/bootstrap-sass or https://github.com/yabawock/bootstrap-sass-rails Thanks in advance!
bootstrap-sass most definitely. Support for Bootstrap 2.0 was included very quickly (there was a development branch even before the main release)
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..…
Do you have an estimate as to when the print edition will be published?
This draft includes previously unpublished versions of Chapter 10, "User microposts", and Chapter 11, "Following users". The original announcement is here: 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.
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?
Thanks.
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.
The 2nd edition explicitly uses Capybara instead of Webrat. As long as people pay attention to their Gemfiles, they should be fine.
Earlier quoted context omitted.
The 2nd edition explicitly uses Capybara instead of Webrat. As long as people pay attention to their Gemfiles, they should be fine.
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.