bradp / vvv-provision-flipper

:dolphin: Quickly toggle between different VVV provisioning scripts

VVV Provision Flipper

🐬 Quickly toggle between different VVV provisioning scripts

With VVV Provision Flipper, you can easily set up multiple named Varying Vagrant Vagrants provisioning scripts and toggle between them.

This is useful, as you can set a provisioning script, for example, that skips updating the included WordPress version to speed up the process. And then periodically toggle between the quick script and the default version included in VVV.

Using the default quick profile, I was able to bring my provision time down to just 21 seconds, vs the normal 300+ seconds. Your mileage may vary.

Installation

To install, you'll want to add the flip file above to your $PATH. In your terminal, simply do $ echo $PATH and save flip in one of those folders. You may have to $ chmod +x flip in the directory you save as well.

Homebrew installation is planned for the near future.

Usage

The first time you run flip you will be prompted to confirm your VVV path. This process will also set up a scripts folder inside of the provision folder in your VVV installation ( <your-vvv-path>/provision/scripts). Two files will be created, sample and quick. sample will be a copy of the VVV provision script, ready for modifications. quick is a trimmed-down version of default script.

By placing any scripts into this folder, you are able to quick use them as your main provision script by running flip set <name>. To use the quicker version, simply run 'flip set quick'

To reset to using the normal provision script, simply run flip reset.

vvv-provision-flipper's Issues

Issue with VVV2 and Provisioning

Seems there is an issue with using VVV Provision Flipper and the develop branch of VVV - if I use flip and set the provision script to quick

Provisioning seems to take longer than normal, output is below, the site is created but an error is output.

==> default: nginx: [emerg] directive "root" is not terminated by ";" in /etc/nginx/custom-sites/vvv-auto-testwithrepo-provision-bf772b3b1b6331f0c76bfd391db43f06.conf:12
==> default: nginx: configuration file /etc/nginx/nginx.conf test failed
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
[Success] New VVV Site Setup: Done!

If you reset the provision script back or use the master branch of VVV then no error occurs.

Claims to update hosts but no sir

This is an awesome addition to VVV.. it speeds up my site creation from 5-10+min to ~1min.

However there seem to be an issue with writing to the hosts file.
It claims to do it in the log just like an ordinary vagrant up but it doesn't. It will also not ask for password even if it should which I suspect is part of the reason why it fails.

To reproduce:

• Setup a new site/project inside www with the vvv-init.sh, vvv-nginx.conf and vvv-hosts files.
• Run flip set quick
• Run vagrant provision

It will log things like
==> default: * Added vvv.dev from /srv/www/vvv-hosts ==> default: * Added local.wordpress.dev from /srv/www/vvv-hosts ==> default: * Added local.wordpress-trunk.dev from /srv/www/vvv-hosts ==> default: * Added src.wordpress-develop.dev from /srv/www/vvv-hosts ==> default: * Added build.wordpress-develop.dev from /srv/www/vvv-hosts
and the new site but the new site will not be added to the hosts file if checked manually afterwards (it will also not work in the browser).
sudo nano /private/etc/hosts