Update README to 0.5-working
Skip all package installation in provisioning after initial boot

Creates a /home/vagrant/initial_provision_run file to track once provisioning has been run on a box for the first time. If this file exists, all apt and composer packages are skipped. Only file linking and WordPress management remains.

If the box is ever destroyed, this flag will be deleted and provisioning will run on the next boot.

See #40
Remove apt_update_run flag in favor of initial_provision_run

Now that all package installation is wrapped in an initial run flag, the check for apt-get update having been run can be removed.

See #40
Add a changelog file
Use the powers of Ruby to provide for a custom Vagrantfile

As the initial Vagrantfile loads, we check for the existence of a Customfile that can contain additional Vagrant configuration parameters. If this file does not exist on your local system, nothing is loaded.

May be useful especially for mapping other drives on the system to setup advanced configurations.

Will need to test whether it will overwrite previously set configuration options in the Vagrantfile
Refresh of README docs
Add Mockery's dependency directly to the composer file.

Composer won't load repository definitions that aren't in the main composer.json file, so we need to include it from Mockery's composer.json file
Merge pull request #43 from johnpbloch/composer

Add Mockery's dependency directly to the composer file.
Update README with proper GitHub links after move to 10up
Merge branch 'develop' of github.com:10up/varying-vagrant-vagrants into develop
Updated notes on Customfile use in Vagrantfile
There's something wrong with me and how I like to order these by line length
Better notes on why the provision flag exists
Updated CHANGELOG for 0.5 release
Updated README for 0.5 release
Merge pull request #45 from 10up/develop

Merging v0.5 from develop branch