Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

PHP Laravel 4 Basics Getting Started with Laravel Installing Laravel

Posted by James Ginns
James Ginns
2,731 Points

Couldn't create vagrant environment in Ubuntu 12.04

I had difficulty generating a vagrant environment on my computer. Steps that I believe contributed to problem:

  1. I did not initially figure out where and how to generate my SSH keys the first time around. I put them in a different folder and named them differently.
  2. I tried editing the Homestead.yaml to reflect the changes in keys. I didn't quite understand the yaml file, so I probably gave it bad key and authorization info
  3. I used the vagrant up command. From the error message it seems the ruby script took the bad info from the yaml file. Instead vagrant told me I either had no vagrant environment. I checked with "vagrant global-config" and no environments show up.

(unrelated, my version of ubuntu didn't have a ruby interpreter, but I have ruby 1.9.3 installed now).

James Ginns
James Ginns
2,731 Points

I managed to succeed by upgrading my distro and NOT using virtual box / vagrant. If anyone also deals with a similar problem, know this: it's not a particularly good idea to use a virtual LAMP stack when you have put together a LAMP stack natively. Current versions of Laravel work based on the packages provided in Ubuntu's current LTS. (the version of PHP, MySQL, etc.)

Btw way, both Homestead and Vagrant are a nightmare if you don't know what you're doing. I think it was a bad decision to introduce so many things that can break into a course with PHP when an updated LAMP stack (and presumably a working install of XAMPP), are much easier to install and configure.