Curious. It doesn't sound like vagrant was able to complete the provisioning. Sometimes launching a vagrant VM initially can take an exceptionally long time especially if it has to download data from the internet. I've had a VM take hours to complete.

You can try asking vagrant to run the provisioner:

First, shut down the current VM if it isn't already.

treehouse $ vagrant halt
==> default: Attempting graceful shutdown of VM...

Then run the provisioner again.

treehouse $ vagrant provision

If that doesn't work, try to destroy and rebuild the VM

treehouse $ vagrant destroy
default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Destroying VM and associated drives...

Rebuild the VM from scratch.

treehouse $ vagrant up

Hopefully that helps!

Hmm it may be that the Vagrant file is corrupt - and requires a treehouse tech to take a look at it.

In the meantime, you can provision your own if you'd like:

Setting up Vagrant

1. Create a new directory for your vagrant and change directory.

$ mkdir vagrant-rails
$ cd vagrant-rails

1. Initialize your vagrant. This goes out to the internet and grabs the popular ubunty/trusty64 vagrant box.

/vagrant-rails $ vagrant init ubuntu/trusty64

One thing you'll want to do, is open your Vagrantfile and add the last line.

# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
config.vm.network "forwarded_port", guest: 3000, host: 3000

1. Launch the vagrant

/vagrant-rails $ vagrant up

1. SSH into the vagrant

/vagrant-rails $ vagrant ssh

Then you can follow the instructions at gorails.com/setup/ubuntu/14.04 to install Ruby using rbenv, then Rails. I'd suggest sticking with SQLite3 for the tutorials, as setting up a database is a pretty deep rabbit hole you may not want to travel down.

Working with your Vagrant

Navigate to the shared folder from inside your vagrant:

$ cd /vagrant

You should see your Vagrantfile in this directory.

Now create your rails application:

vagrant/ $ rails new myapp

This will create your rails application in the shared directory.

Launch your Rails Server

One "gotcha" is when you launch you rails server you will need to bind thte server to 0.0.0.0

$ rails s -b 0.0.0.0

Now if you go to localhost:3000 in your browser, you should see the Welcome to Rails screen.

Work with Rails

Okay, so now that you've got your initial application set up, what now?

1. Open a new terminal tab with Command + T on a mac.
2. Navigate to your /vagrant-rails directory. You should see your rails application folder.
3. Navigate into your project directory

vagrant-rails/ $ cd myapp

1. Launch your editor

vagrant-rails/myapp/ $ subl .

And viola! You can now work with your Rails application.

I typically use git from my mac (not from vagrant) to manage my codebase as well.

Excellent Gary! In the meantime, I'll ask Nick Pettit to follow up for you on the status of the Teamtreehouse vagrant.