Please read for an updated status on RailsCasts:
Learn more or hide this
Am I missing something or does the Homebrew install need Ruby, which you then go on to recommend installing using rvm?
Homebrew shouldn't need ruby. It's just a nice packaging system over macports for mac. For instance you can install mysql , libxml2, etc from homebrew. You can just go to the rvm site, run the instructions in your terminal to setup rvm. Rvm is for managing ruby versions . Install ruby through rvm . Nothing is dependent of homebrew here.
OSX is shipped with precompiled Ruby 1.8.7. Homebrew uses ruby files (called recipes) to execute bash statements. Though, Ruby is preinstalled on MacOS, developers prefer using RVM to manage ruby versions/gemsets.
As usual thx Ryan!
I think this is a really interesting screencast about rails and its environment.
Recently I switched from Rails to Playframework (Java) for most of my projects. Did you ever think about making screencasts for other frameworks as well?
Railscast is a really valuable resource for rails and it would be great to find something for playframework as well :D
Another excellent Ruby resource is Ruby Koans
yes, and it's also definitely worth checking out Ruby Monk as well as The Ruby Game
Confused about what version of Ruby to use. I thought it was suggested to use 1.9.2 for Rails 3 and 3.1, but I see you are using 1.9.3. Does it matter which is used? Is 1.9.3 better?
Great screencast Ryan!
I've also written a zero to hero guide on my blog (it's now also returned with the help! factoid in the official rails chat room) - check it out here: Best Way to Learn Ruby & Rails
I think there is a small mistake for the Linux command to set the default Ruby version, instead of global you should use default:
rvm use 1.9.3 --default
rvm use 1.9.3 --default
Great episode Ryan! I really like the introduction of Basalmiq as I've just discover this tool!
I would really LOVE to see some Ruby screencasts here (even if it's "Rails"-cast), starting with basics to metaprogramming. It could be a great, great addition associated with your "classic" rails screencasts.
I have to say my bigger problem is, even after reading few ruby books, that is still hard (for me) to understand how rails does things under the hood, and to understand WELL all parts of the framework. To be more explicit, Rails does things, but I often question myself with why? and how? (And I think most of this is because I am not enough proficient in Ruby - However, I have to say I'm starting to understand rails better through the study of another framework/language, as I started with rails/ruby)
Your episode 299: "Rails Initialization Walkthrough" was a great starting point of what I mean, and it could be awesome to see more screencasts like this in the future ;) Thanks!
What I mean with my last quote is the following: The idea is NOT to know how to build, for example, Active Record, but understanding better the code and the process - through a reading for example?
I wish I had had this when I was first learning Rails. I felt pretty lost, and this is exactly the information I could have used.
I didn't know about Balsamiq, I'll definitely be trying that out on my next project.
Thanks for another awesome cast!
I highly recommend The Intro to Rails Screencast I Wish I Had by Jeffrey Way
Thanks Ryan, hope this type of episodes we will see more in future. While doing development we come across issues, day to day troubleshooting, issues faced, new findings, concepts which I have shared with rest of the world through http://rorguide.blogspot.com/. Hope this will be helpful to beginners too.
One thing - do you not need to install Xcode first to allow rvm to work?
(Just for context: I'm running SnowLeopard on an older machine. I did have a working installation but naiively thought I could get away with uninstalling Xcode once I'd installed Homebrew)
The Xcode install comes with gcc which is needed for compilation. You might be able to install gcc separately and get everything working smoothly. gcc isn't listed as a dependency of rvm, but I'm pretty sure it is required to make the rubies.
If anyone could add some notes on Windows installation, feel free.
It's been awhile since I started with Rails, and I use pik; but I'm still finding upgrading to 1.9.3 a challenge.
What problems have you found?
Just getting things set up right. I know I had to add devkit before; and that there's some tweaking of environment variables; but no clear set of steps to follow. There is a pik devkit command, which throws an error.
Hmm. There is this,
which reminded me to edit devkit\config.yml and add the new ruby location, e.g.
Maybe that's what pik devkit was supposed to do for me!
Also the Windows testing/autotesting setup has many dead-end rabbit holes.
Don't bother trying to run Rails on Windows. I spent a few days trying to get it to work, and it just doesn't. It takes 10 minutes for Rails to start, and many gems don't work.
If you are new to Rails, trying to use Windows makes it much harder. And Rails is hard enough.
I installed Ubuntu (which can run on the same machine) which works well for Rails. Or, find an old machine and run Ubuntu on it. I ended up using sharing the source folder and using Notepad++ on my regular dev machine which works well.
The only real improvement is to get a Mac and run TextMate. But this solution is 90% there.
Another option is to use Vagrant, which is what I use when I develop Ruby applications on Windows.
a wonderful framework
First sign in through GitHub to post a comment.