bryannielsen / laravel4-vagrant Goto Github PK

View Code? Open in Web Editor NEW

488.0 39.0 136.0 9.75 MB

Run Laravel4 inside a Ubuntu 12.04 Vagrant Virtual Machine w/PHP 5.5

Puppet 19.04% Ruby 48.75% Shell 0.85% Pascal 0.35% PHP 0.98% HTML 30.04%

laravel4-vagrant's Introduction

Laravel 4 w/ Vagrant

A basic Ubuntu 12.04 Vagrant setup with Laravel4 and PHP 5.5. PHP 5.4 w/ Apache 2.2 is available on the php54 branch.

Requirements

VirtualBox - Free virtualization software Download Virtualbox
Vagrant 1.3+ - Tool for working with virtualbox images Download Vagrant
Git - Source Control Management Download Git

Setup

Clone this repository git clone http://github.com/bryannielsen/Laravel4-Vagrant.git
run vagrant up inside the newly created directory
(the first time you run vagrant it will need to fetch the virtual box image which is ~300mb so depending on your download speed this could take some time)
Vagrant will then use puppet to provision the base virtual box with our LAMP stack (this could take a few minutes) also note that composer will need to fetch all of the packages defined in the app's composer.json which will add some more time to the first provisioning run
You can verify that everything was successful by opening http://localhost:8888 in a browser

Note: You may have to change permissions on the www/app/storage folder to 777 under the host OS

For example: chmod -R 777 www/app/storage/

Usage

Some basic information on interacting with the vagrant box

Port Forwards

8888 - Apache
8889 - MySQL
5433 - PostgreSQL

Default MySQL/PostgreSQL Database

User: root
Password: (blank)
DB Name: database

PHPmyAdmin

Accessible at http://localhost:8888/phpmyadmin using MySQL access credentials above.

PHP XDebug

XDebug is included in the build but disabled by default because of the effect it can have on performance.

To enable XDebug:

Set the variable $use_xdebug = "1" at the beginning of puppet/manifests/phpbase.pp
Then you will need to provision the box either with vagrant up or by running the command vagrant provision if the box is already up
Now you can connect to XDebug on port 9001

XDebug Tools

MacGDBP - Free, Mac OSX
Codebug - Paid, Mac OSX

Note: All XDebug settings can be configured in the php.ini template at puppet/modules/php/templates/php.ini.erb

Vagrant

Vagrant is very well documented but here are a few common commands:

vagrant up starts the virtual machine and provisions it
vagrant suspend will essentially put the machine to 'sleep' with vagrant resume waking it back up
vagrant halt attempts a graceful shutdown of the machine and will need to be brought back with vagrant up
vagrant ssh gives you shell access to the virtual machine

Virtual Machine Specifications

OS - Ubuntu 12.04
Apache - 2.4.6
PHP - 5.5.4
MySQL - 5.5.32
PostgreSQL - 9.1
Beanstalkd - 1.4.6
Redis - 2.2.12
Memcached - 1.4.13

laravel4-vagrant's People

Contributors

Stargazers

Watchers

Forkers

niallobrien coreymcmahon cpjobling moki9 mjaschen stefanneubig thed1360 firework nealerickson sineld mattam danmatthews phirschybar fhferreira djuki pedrocifuentes axent rjsamson infabinho jjclane applecrusher metafuse hsnk dreadpiratejay marcusbrose timlindsay bradstinson wordpressdev prik waynoss lscott3 dragonfire1119 40thieves cfgt sthomashh johnnncodes fabriziomachado jasonmichels trojanspike tomazxz dgreda ingeting xteam-zack fachriza leonwiskie packettide brianrhea compusam peb7268 alan-zhang- deens witq fierroformo dschniepp pinneo andrewmclagan chris911 colinorr everdaniel noahjs globegitter heera jbuc bsormagec brainv okanimamoglu eightypop hearsay aeholmes vernard couldtt joanteixi t-vieira shorman torontotoollibrary rikh42 phuang07 bmartel rjbautista danielsum gayanhewa elasticbrains-dn mandofever78 bennyboy121 karkoonzaid cbking jeffreyvdb dhatch6 laksamanakeris csjoblom carnedv doridoridoriand amazinghorse cvongrim bobo52310 david-macias crankeye nanigans leoclaro nrmjba

laravel4-vagrant's Issues

Error when running "php artisan migrate"

Hi bryannielsen,
I used Ubuntu 14.04, latest HHVM , nginx1.6, php 5.5 and mysql 5.5.
When I run "php artisan migrate", I got an error like this image:
https://imageshack.com/i/ipECg4Fpp

So, in Migrations directory I have a file with content:

class CreateUsers extends Migration {

/**
 * Run the migrations.
 *
 * @return void
 */
public function up()
{
    Schema::create('users',function($table){
        $table->increments('id');
        $table->string('username',60);
        $table->string('password',66);
        $table->integer('level')->default(1);
        $table->timestamps();
    });
}

/**
 * Reverse the migrations.
 *
 * @return void
 */
public function down()
{
    Schema::drop('users');
}

}

Not sure if its something i've done wrong but any suggestions would be appreciated!
Kevin

Setup default MySQL database

Get a db setup using the default settings from illuminate/app

I have got the following errors

I am getting the following errors

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' --manifestdir /tmp/vagrant-puppet/manifests --detailed-exitcodes /tmp/vagrant-puppet/manifests/phpbase.pp || [ $? -eq 2 ]

Stdout from the command:

Question: UTC Timezone

I see the Vagrant file has one line with "--rtcuseutc", "on"

Later in the file, the timezone is set to America/NewYork.

lv4_config.vm.provision :shell, :inline => "echo \"America/New_York\" | sudo tee /etc/timezone && dpkg-reconfigure --frontend noninteractive tzdata"

If I delete this line, will all times be interpreted as UTC & would that create any problems with Laravel?

ssh root account

Whats the password for the root account?

Setting up vhosts not working

in /etc/hosts I added:

127.0.0.1       localhost laralaunch.dev
127.0.1.1       laravel laravel precise32 laralaunch.dev

and in /etc/apache2/sites-enabled/000-default.conf, I have:

<VirtualHost *:80>
        ServerName   laralaunch.dev
        DocumentRoot /var/www/public

        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>

        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride All
                Order allow,deny
                allow from all
        </Directory>

        ErrorLog /var/log/apache2/error.log
        LogLevel warn
        CustomLog /var/log/apache2/access.log combined
</VirtualHost>

But when I restart apache, the domain just does not catch. What am I doing wrong? How do I fix this?

Initial database configured incorrectly

The password for mysql is root but the one configured in app/config/database.php is empty. Wouldn't it be best to have it pre-configured with the correct password?

EDIT: probably solved [Exception] date.timezone not set in php.ini

[EDIT]
Looks like it has been solved with the #33 fix
[/EDIT]

I get this error in my php_error.log:
Exception: DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.

Since in the vagrantfile i can see this:
lv4_config.vm.provision :shell, :inline => "echo "America/New_York" | sudo tee /etc/timezone && dpkg-reconfigure --frontend noninteractive tzdata"

i will see if there's a way to put the same setting in php.ini

No data received

After running vagrant up then tried to access http://localhost:8888/ i get No data received error.

[get laravel packages] breaks during the Puppet initialization

Firstly, thanks for setting up this Vagrantbox.
After cloning your github repository, and running 'vagrant up', Puppet appears to start initializing stuff. But at a certain point, it hits an error (possibly related to "get laravel packages") I've included the end of the Puppet initialization run:

notice: /Stage[main]/Apache/Service[apache2]: Triggered 'refresh' from 4 events
notice: /Stage[main]/Laravel_app/Exec[install composer]/returns: executed successfully
notice: /Stage[main]/Laravel_app/Exec[global composer]/returns: executed successfully

err: /Stage[main]/Laravel_app/Exec[get laravel packages]/returns: change from notrun to 0 failed: /bin/sh -c 'cd /var/www/ && composer install' returned 1 instead of one of [0] at /tmp/vagrant-puppet/modules-0/laravel_app/manifests/init.pp:29

notice: /Stage[main]/Laravel_app/Exec[get laravel updates]: Dependency Exec[get laravel packages] has failures: true

warning: /Stage[main]/Laravel_app/Exec[get laravel updates]: Skipping because of failed dependencies

notice: /Stage[main]/Php/Package[php5-dev]/ensure: ensure changed 'purged' to 'latest'
notice: Finished catalog run in 486.18 seconds

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && puppet apply --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/phpbase.pp --detailed-exitcodes || [ $? -eq 2 ]

Then it kicks me back out to my commandline. Any clues for how to fix this?

Errors with new installation on Mavericks

Hello! I updated my system (new install, not upgrade) to Mavericks and there are something wrong when provisioning the box. It takes 2179.28 seconds to provisioning and I think that the problem is here:

err: /Stage[main]/Laravel_app/Exec[create laravel project]/returns: change from notrun to 0 failed: Command exceeded timeout at /tmp/vagrant-puppet/modules-0/laravel_app/manifests/init.pp:35 (at this point stops during 10 minutes or more)

When i go to localhost:8888 i see a white page

I paste the last log lines:

notice: /Stage[main]/Apache/File[/etc/apache2/mods-enabled/rewrite.load]/ensure: created
notice: /Stage[main]/Laravel_app/Exec[clean www directory]/returns: executed successfully
notice: /Stage[main]/Phpmyadmin/File[/etc/apache2/conf-enabled/phpmyadmin.conf]/ensure: created
err: /Stage[main]/Laravel_app/Exec[create laravel project]/returns: change from notrun to 0 failed: Command exceeded timeout at /tmp/vagrant-puppet/modules-0/laravel_app/manifests/init.pp:35
notice: /Stage[main]/Phpmyadmin/Package[phpmyadmin]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Phpmyadmin/File[/etc/phpmyadmin/config.inc.php]/content: content changed '{md5}f5201f1a5c501d2f0bacc551d9bfedce' to '{md5}fcaa8a6ea29ab87b15c2b588c95ba943'
notice: /Stage[main]/Phpmyadmin/File[/etc/phpmyadmin/config.inc.php]/mode: mode changed '0644' to '0775'
notice: /Stage[main]/Apache/Exec[echo "ServerName localhost" | sudo tee /etc/apache2/conf-enabled/fqdn.conf]/returns: executed successfully
notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/000-default.conf]/content: content changed '{md5}7aca057d3c02f05f0188896e563edd4a' to '{md5}82abd1ac0be7335363e705538a4627f5'
notice: /Stage[main]/Apache/Service[apache2]: Triggered 'refresh' from 8 events
notice: Finished catalog run in 2179.28 seconds

p.d. After, I had installed Lion. I see the same behaviour with a workmate with mountain lion and he desist to use vagrant for this. Before install Mavericks i cannot use this box and my old boxes

Strategy for using git on laravel project when using git to manage Laravel4-Vagrant

My plan is to manage the changes I make to laravel4-vagrant using git, but I also want to manage my laravel changes using git. I am not quite sure how to set this up as /var/www is ignored and that is where my work would be. Can I start a git repo there somehow so that way outside of the VM I can use git to then manage a specific laravel project? e.g., I want to be able to vagrant up, do some work, manage my work in git, have my laravel project saved outside of the vm, and be able to redeploy via vagrant and then load up my laravel git repo. How is the best way to go about doing this, or should I be following a different game plan?

Install Memcached, not memcache

Hi!

I testing memcached on laravel but i can not configure it properly.

I think that there is a module missing. Provision install memcache but not memcached (this is which laravel works)

In my laravel project I added this in cache.php inside the app folder
'driver' => 'memcached',

'memcached' => array(
array('host' => '127.0.0.1', 'port' => 11212, 'weight' => 100),
),

in my vagrant file I added a new port forwading
lv4_config.vm.forward_port 11211, 11212

and I added in /puppet/modules/php/manifests/init.pp memcached

$packages = [
    "php5", 
    "php5-cli", 
    "php5-mysql", 
    "php-pear", 
    "php5-dev", 
    "php-apc", 
    "php5-mcrypt", 
    "php5-gd", 
    "php5-curl",
    "libapache2-mod-php5",
    "php5-xdebug",
    "php5-memcache",
    "php5-memcached",
    "php5-pgsql",
    "php5-sqlite"
]

And then I provisioning my box and see with php -v that all are correct installed

Are you able sometime to work with memcacheD with laravel?

working with docker & vagrant in windows

after clone using command "git clone https://github.com/dotcloud/docker.git"
"cd docker"
following issues are not resolved.... please any one fix the issue....
"vagrant up" command is not working
issues as follows:

D:\docker>vagrant up
Vagrant failed to initialize at a very early stage:

The home directory you specified is not accessible. The home
directory that Vagrant uses must be both readable and writable.

You specified: C:/Users/Acer/.vagrant.d

Request: `php artisan` alias

I would submit a pull request for this one, if I knew how to do it - but I don't.. sorry.

Anyway, I think it would be worth adding a .bashrc alias which maps php artisan to art. This would save our keyboards and keyboards a little bit of wear and tear :)

change "extra" to "mount_options"

in vagrantfile I had to change "extra" tag to
mount_options => ["dmode=777","fmode=777"])

so line will be as follow

lv4_config.vm.share_folder("www", "/var/www", "./www", :mount_options => ["dmode=777","fmode=777"])

Chrome Failed to Load Resource

Occasionally I'm seeing a bunch of "Failed to Load Resource" errors in the chrome web inspector, they usually appear 3-5 seconds after the page has loaded successfully.

It doesn't seem to affect the page rendering and the last activity in the network pane indicates the page loaded with a 200 status.

This only happens with PHP files (straight HTML are fine) so it must be an issue with the php5 apache module. Haven't seen this happen in Firefox or Safari.

PHP XDebug Not working

Following:

"To enable XDebug:

Set the variable $use_xdebug = "1" at the beginning of puppet/manifests/phpbase.pp
Then you will need to provision the box either with vagrant up or by running the command vagrant provision if the box is already up
Now you can connect to XDebug on port 9001"

Instructions doesn't result in being able to connect to xdebug on port 9001. In both cases of a fresh vagrant up, or a vagrant up and then vagrant provision, telnet to port 9001 in the vagrant itself results in "Unable to connect to remote house: Connection refused"

root@laravel:~# telnet localhost 9001
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

Laravel4-Vagrant on Windows

I dont know why, but for some reason, this line never gets executed on my Windows maschine:

lv4_config.vm.provision :shell, :path => "puppet/scripts/enable_remote_mysql_access.sh"

If I put it right behind the other provision line: "lv4_config.vm.provision" it works though.

Can anybody explain this behaviour?

Connect via Sequel Pro or Navicat

Just wondering how to do this if it's not already possible. Don't really want to SSH tunnel into the vagrant box to do so

Puppet Issues

We had some errors crop up today on a few boxes based on Laravel4-Vagrant - my best guess is that the php versions in the repo got bumped from 5.4.x to 5.5.x, which in turn changed a bunch of other dependencies (requiring Apache 2.4 for example) - I don't know puppet well enough to know how to limit the php version to 5.4.x, but I'm guessing that's what has to be done.

Any guidance you could provide would be great. below is a dump of the errors:

[laravel4] Running provisioner: puppet...
Running Puppet with phpbase.pp...
stdin: is not a tty
err: /Stage[main]/Laravel_app/Exec[get laravel updates]/returns: change from notrun to 0 failed: /bin/sh -c 'cd /var/www/ && composer update' returned 255 instead of one of [0] at /tmp/vagrant-puppet/modules-0/laravel_app/manifests/init.pp:41
notice: /Stage[main]/Php54/Exec[php54 apt update]/returns: executed successfully
notice: /Stage[main]/Php54/Exec[add php54 apt-repo]/returns: executed successfully
notice: /Stage[main]//Exec[apt-get update]/returns: executed successfully
notice: /Stage[main]/Php/Package[php5-mysql]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
notice: /Stage[main]/Php/Package[php5-gd]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
notice: /Stage[main]/Php/Package[php-apc]/ensure: ensure changed '3.1.13-1~precise+1' to '4.0.1-4~precise+1'
notice: /Stage[main]/Php/Package[php5-mcrypt]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
notice: /Stage[main]/Php/Package[php5-xdebug]/ensure: ensure changed '2.2.1-1~precise+1' to '2.2.3-1~precise+2'
notice: /Stage[main]/Php/Package[php5-memcache]/ensure: ensure changed '3.0.6-5~precise+1' to '3.0.8-1~precise+2'
notice: /Stage[main]/Php/Package[php5]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
notice: /Stage[main]/Php/Package[php-pear]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
notice: /Stage[main]/Php/Package[php5-pgsql]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
notice: /Stage[main]/Php/Package[php5-curl]/ensure: ensure changed '5.4.17-1~precise+1' to '5.5.1+dfsg-1~precise+1'
err: /Stage[main]/Php/Package[libapache2-mod-php5]/ensure: change from 5.4.17-1~precise+1 to 5.5.1+dfsg-1~precise+1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libapache2-mod-php5' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libapache2-mod-php5 : Depends: apache2-api-20120211 but it is not installable
                       PreDepends: apache2 (>= 2.4)
E: Unable to correct problems, you have held broken packages.
 at /tmp/vagrant-puppet/modules-0/php/manifests/init.pp:25

Lost connection to MySQL server

Hi I have two projects using this vagrant setup. It's great thanks.

for some reason one project I can't connect with Navicat or a desktop sql client. The other connects no problem. The most recent vagrant setup is the one causing the sql desktop connection problems, the other one i setup earlier in the summer.

on the problem vagrant setup i get this error from navicat: Lost connection to MySQL server at 'reading initial communication packe…

Has anything changed in this vagrant setup in the last couple months that would prevent sql clients from connecting? Change to firewall settings for example?

Sync the app/storage folder with proper owner/group instead of leaving it to the user

# Set the ownership of the app/storage directory
config.vm.synced_folder "app/storage", "/vagrant/app/storage", :owner => 'www-data', :group => 'www-data'

This sets the /vagrant/app/storage permissions so you don't need to constantly chmod/chown.

Vagrant fails to initialize

After cloning the repo and running vagrant up in the directory it creates, I'm immediately getting an error:

➜  Laravel4-Vagrant git:(master) vagrant up
Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/casey/Build/Laravel4-Vagrant/Vagrantfile
Message: cannot load such file -- vagrant/command

CLOSE THIS: undefined local variable or method `v' for main:Object

Fresh clone, cd into new directory... vagrant up... super fast error.
EDIT : somehow I must have accidentally fat-fingered the file... nevermind! :)

With phpdebug=1, the webserver is too slow sometimes

When phpdebug=1 it takes more than three minutes to serve the website and I cannot use xdebug, the xdebug log shows the connnectin with the client but don't works.

Have you problems with this?

Request: HHVM

Do you think you can bake some support for HHVM into the box?

I'm not sure that it is a suitable alternative to PHP for anything accessed via the web interface/apache - but I've heard that it is really fast for running CLI stuff.

It could be good to have as an alternative to the php command via the CLI, allowing for commands to be run via hhvm artisan migrate (or whatever)

Just a thought :)

Doesn't work on Windows 7

Hey, I just tried running this, but there is no response on localhost:8888 . I had the "DL is depraced, use Fiddle" messages. So I tried to install Ruby 1.9.3 and have added it to system path. I was also able to "vagrant ssh". I tried this with Vagrant 1.4.3 at the beginning and then I tried Vagrant 1.3.5, but with that, installation finished, but there were many failed dependencies errors.

I was also getting "Could not retrieve fact fqdn" warning and "Stderr from the command: stdin: is not a tty". No clue here.

Is there anybody running this on Windows? It looks really great, but as a Vagrant newcomer, it's quite hard to figure out where is a problem.

New pulls from this repo are broken.

There is an issue with the new compiled.php file (I think although it could be occurring elsewhere) that needs a composer update to fix.

Artisan commands from host

Setup a vagrant command to pass artisan commands through to the laravel setup. Something like vagrant artisan migrate would be nice. Currently the closest way to do this currently is vagrant ssh -c "php /var/www/artisan list"

No Connection could be made because the target machine actively refused it.

I get this error when i try to migrate the db I have no clue how to fix this .

Nginx varient

Would be super cool to have an Nginx varient as aposed to Apache. Don't know whether I should just fork and change myself, or if you could just add it in alongside Apache (different port)?

Migrate error [ErrorException] Undefined variable: table

Hey,

Getting an error when running php artisan migrate:

[ErrorException]
Undefined variable: table

migrate [--bench[="..."]] [--database[="..."]] [--path[="..."]] [--package[="..."]] [--pretend] [--seed]

Not sure if its something i've done wrong but any suggestions would be appreciated!

Joe

Add Postgres and Memcache

config.vm.customize calls are VirtualBox-specific

I'm pretty new to vagrant / virtualbox but i'm getting this error message when I run vagrant up

There were warnings and/or errors while loading your Vagrantfile.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.

Warnings:
* `config.vm.customize` calls are VirtualBox-specific. If you're
using any other provider, you'll have to use config.vm.provider in a
v2 configuration block.

Forward SSH Agent

Need to do this so that we can install private composer packages to which the host machine has public key access.

Can't connect to postgresql from my local machine

Hello,
I just installed the Laravel4-Vagrant box !
All is running well but I can't connect to the postgresql database from my local machine (I'm using Pgadmin3).
This is the information that I'm using :
host : localhost
port : 5433
user : root
password : I can't use no password as described in the doc so I use "root" again

Pgadmin3 tells me that "Server doesn't listen".

Thanks in advance !

Add Sqlite database in memory

Hello, i'm asking if you could add sqlite in memory support for the vagrant machine.
Thanks!

Jacopo

Can't access phpmyadmin

After installing https://github.com/liebig/cron (by following the steps given) I am unable to visit phpmyadmin via the usual http://localhost:8888/phpmyadmin

Instead I get a a stack trace - NotFoundHttpException. Still looking into it but any help is much appreciated :-)

sqlite PDO driver missing

Hi, me again, sorry about this.

Just a quick one, but the box doesn't have the PDO drivers for sqlite installed by default. This can be easily fixed by running sudo apt-get install php5-sqlite on the command line (or the puppet equivalent).

This wouldn't normally bother me (I've never used sqlite), but I'm reading Laravel Testing Decided by Jeffrey Way (very good book) and he talks about using an sqlite database in memory for testing purposes, which seems like a very good idea.

(I would submit a pull request for this, but, alas, I have no idea how to achieve this).

Can you please install phpPgAdmin?

Thanks you!!!

xdebug port

why not leave the xdebug port at 9000. There will be no conflict because the vagrant server is using that port to contact the host. Right?

Laravel directory not mapped correctly to /var/www

It seems that local edits to Laravel code (ie routes.php edits) dont get mirrored to host /var/www? The initial setup is accurate, but future changes dont seem to work correctly.

I have tried to perform a symlink but doesn't work?

ln -fs /vagrant /var/www

Any recommendations here?

In short, apache2 is using /var/www as the home directory, but edits performed locally are shared to /vagrant directory (which is correct as far as I can tell) So, how can I get /vagrant to point to /var/www (again the link I have created doesnt work)

I have also tried:

rm -rf /var/www ln -fs /vagrant /var/www

But, when restart apache sudo service apache2 restart it gives an error starting access denied to '/public' directory?

Should composer be part of its own manifest instead of the laravel one?

I really like the look of this vagrant box and am going to use it myself for projects (laravel and other non-laravel ones).

I've never really used puppet before but being it seems like installing laravel and installing composer should be 2 seperate steps (especially considering its a global installation of composer).

So something like puppet/modules/composer/manifests/init.pp

class composer
{

    package { 'git-core':
        ensure => present,
    }

    exec { 'install composer':
        command => 'curl -s https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin',
        require => Package['php5-cli'],
        unless => "[ -f /usr/local/bin/composer ]"
    }

    exec { 'global composer':
        command => "sudo mv /usr/local/bin/composer.phar /usr/local/bin/composer",
        require => Exec['install composer'],
        unless => "[ -f /usr/local/bin/composer ]"
    }
}

I wanted to get others thoughts on this before submitting a PR

Lack of default mysql password prevents access via phpMyAdmin

As stated in the title, because the default settings for mysql don't include a password for the root user, you're unable to log into phpmyadmin because it's config is set to prevent passwordless logins.

I can see three ways off solving this issue:

Set-up a default password for the root user.
Change the default config for phpmyadmin to allow passwordless logins.
Provide some instructions on how to set your own password for the root user.

Personally, in this instance, I went for the 3rd option, following these instructions, which worked - although I'm sure there is no-doubt a far batter way of doing this.

Install Laravel 4 throught Composer

Wouldn't it better now to install Laravel 4 using this command:

composer create-project laravel/laravel

instead of duplicating Laravel's source code in this repo?