Chris Oliver

Yes! That is correct. I'll try to update the tutorial soon to note that. Thanks!

Fixed! Thanks for pointing those out Abe.

If you used rbenv, you'll need to run "rbenv rehash" to get it to see the new version of Rails.

Make sure you haven't installed Rails from another method. It seems as if you've got two copies of Rails installed.

Good to hear, and let me know via email if you have anything that should be changed.

Thanks for the notes! I'll update the tut.

You're missing the autoconf package. Just run sudo apt-get install autoconf and it should work if you try again.

Thanks for the kind words Nes! I've been planning how we're going to do the Rails content with the same sort of clarity and we will definitely be taking you along step by step. Hop on the mailing list and I'll be sure to let you know when they are out. :)

Sounds like curl isn't able to authenticate with your proxy. You might just try adding the proxy credentials into the curl command. You can run man curl in terminal to get the docs on it.

I think you can pretty much follow the MySQL instructions and it is a seamless replacement. Try following those and you should be good.

No, actually you have to set it up. That's sort of where my tutorial leaves off I guess.

Add gem "mysql2" to your gemfile, change the adapter in database.yml to adapter: "mysql2" and add a password line that has the database password. Run bundle install and restart your Rails app and you should be good to go!

You may also need to run rake db:create to have Rails create the database for you.

That's saying that your database connection to the database isn't working. You may have specified a password when you installed MySQL or a different username than root. Update your database.yml to specify the database, make sure you have the mysql2 or pg gem installed in the Gemfile, and you'll be good to go.

Perfectly good! :) Gems get installed to a location like that when you're in development. It's mostly because you shouldn't ever modify the gem's code, so they don't want to place it in a location where you might be tempted. If you do want to modify the gem, you can fork it and use either the github or path options when specifying a gem to user your own version. This didn't make much sense to me either the first time I used it.

It sounds like you're missing the openssl lib and that's causing it to fail. Can you check to make sure you have libssl-dev installed?

Make sure you didn't put this gem or the sass gem inside the assets group because Rails 4 no longer uses it. If that's not it, paste your Gemfile in a gist and I'll take a look!

Thanks Al! I'll be updating the tutorial shortly. I think I wrote it when Rails 4.0 wasn't out yet but hadn't updated it since.

Fantastic! I'll update the tutorial to include this in the near future.

I think it's likely that the editors are looking for the Ruby executables. rbenv and rvm both install hooks into the shell so that you can switch between active Ruby versions. The editors most likely don't execute your shell configuration so it doesn't find them. My suggestion in this case is to choose the version of Ruby you're planning on using and find their binary inside either the .rbenv or .rvm folders inside your home directory. That way it can find the executable directly without having to jump through one of the managers.

That's fantastic to hear! :) Programming really is a blast and I'm glad you got Rails 3 going. You'll be able to upgrade it later on fairly easily anyways. Good luck with everything and let me know if you have any more questions!

I know the feeling. :) So if you go with MySQL, you need to update your database.yml to use the "mysql2" adapter and install the "mysql2" gem with your Gemfile. By default it's going to use sqlite3. You should be able to run fine with sqlite3 so it shouldn't be having any errors. Does your log/development.log file contain any info that might help debug what's wrong?