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 Homestead

Posted by Wendell Pulsipher
Wendell Pulsipher
10,183 Points

What about windows? (laravel)

Hampton Paulk I think you need to show people how to do all of this on a windows as well. So many of us are not familiar at all with git bash or have a very limited understanding of cmd. Just a suggestion

4 Answers

Hampton Paulk
Hampton Paulk
5,093 Points
Hampton Paulk
Hampton Paulk
5,093 Points

Hi Gents. I will gladly shoot a video for the windows install process. Once inside of the virtual machine the remainder of the process will be the same. (This is the great thing about a virtual machine!)

Byron Allen
Byron Allen
7,068 Points
Byron Allen
Byron Allen
7,068 Points

I totally agree

Hampton is an awesome teacher but it puts you off the course right from the start.

ilias Georgakopoulos
ilias Georgakopoulos
22,866 Points
ilias Georgakopoulos
ilias Georgakopoulos
22,866 Points

I want to add also for some cases it is necessary to enable hardware virtualisation (VT-x) from the bios (for some HP laptops mostly). My self i still have problems to finish the installation.

ilias Georgakopoulos
ilias Georgakopoulos
22,866 Points
ilias Georgakopoulos
ilias Georgakopoulos
22,866 Points

I found that the processor in my laptop does not support Virtualization Technology (VT-x). So far i tried to change the

config.vm.box = "laravel/homestead" to config.vm.box = "antoniofrignani/laravel-homestead-settler-32"

which is located under 

Homestead\scripts\homestead.rb

but i get the same error. 

C:\Users\Nemesis\Homestead>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 80 => 8000 (adapter 1)
    default: 3306 => 33060 (adapter 1)
    default: 5432 => 54320 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.