VVV 1.4.1

• No functional changes.
• Introduce a documentation structure for future releases.

VVV 1.4.0

1.4.0 release post

Bug fixes and Enhancements

• PHP 7.0.x has now replaced PHP 5.5.x. See #844.
• Update PHPUnit to the latest stable 5.6.x version. See #1004
• Xdebug 2.4.0 is now built from source to provide PHP 7.0.x support. See #869.
• Disable Xdebug during provisioning so that Composer can operate at normal speed. See #971
• Improve the package installation check to avoid false positives. See #840.
• Allow vvv-nginx.conf to be located in a project's subdirectory. See #852.
• Install the latest version of git via its PPA. See #872
• Assign names to pre, custom, default, and post provisioners to make --provision-with possible. See #806
• Install nvm to provide access to multiple NodeJS versions. See #863
• Provide the NodeJS 6.x LTS release by default. See #1007
• Switch to NodeSource for NodeJS packages. See #779
• Move query_cache_* config for MySQL to its proper place in the [mysqld] section. See #925
• Allow WordPress core unit test database configuration to be supplied with environment variables. See #846.
• Use the correct command wp core update when updating WordPress with WP-CLI. See #958
• Remove the core.svn.wordpress.org WordPress trunk checkout from default provisioning. develop.svn.wordpress.org remains. See #921
• Checkout and initialize the develop.svn.wordpress.org repository in a temporary (non-shared) directory. This addresses issues with a possible race condition during NPM package installation on a shared drive. See #969

VVV 1.3.0

1.3.0 release write-up

Features

• Add support for Parallels as a provider. See #479.
• Add support for Hyper-V as a provider. See #742.
• Add support for VMWare Fusion as a provider. See #587.
• Add support for VMWare Workstation as a provider. See 656.
• Add MailCatcher to default provisioning. See #632.

Bug fixes and enhancements

• Composer: Set a custom GitHub token for Composer if it exists. See #575.
• Docs: Update inline Vagrantfile documentation to better explain various network configurations.
• MySQL: Enable innodb_file_per_table. See #537.
• npm: Add npm-check-updates during provisioning to help manage package.json inside the VM. See #484.
• PHP: Bump max upload size in PHP and Nginx to 1024MB to support developing on the Internet in the year 2016. See #599.
• PHPCS: Set default code standards for PHPCS to WordPress-Core. See #574.
• phpMyAdmin: Allow for a custom phpMyAdmin configuration file. See #688.
• PHPUnit: Update PHPUnit to 4.8.x. A future update of VVV should include PHP 5.6.x or PHP 7 and allow us to update PHPUnit to 5.x. See #808.
• PHPUnit: Allow PHPUnit to run tests from the local machine while using the WordPress unit tests database in the virtual machine. See #785.
• PHPUnit: Set the WP_CORE_DIR path so PHPUnit tests are run against WordPress trunk. See #783.
• Provision: Rewrite provision.sh to be more modular. This improves readability and may one day aid in testability. See #659.
• Vagrant: Set the default box name to that of the working directory to allow for multiple instances of VVV without conflict. See #706.
• Vagrant: Allow for a custom trigger, vagrant_up to fire during vagrant up and vagrant reload. See #778.
• Vagrant: Make it easier and more forward-compatible to modify the virtual machine's IP address. See #781.
• Vagrant: Clarify default setting of 1 CPU when creating the virtual machine. See #625.
• WordPress: Provide better support for testing with xip.io by accounting for these requests in wp-config.php. See #559.
• WordPress: SVN repositories configured in VVV provisioning are now set to HTTPS. Existing repositories configured to HTTP will not automatically update during provisioning unless they are first relocated to HTTPS. The svn relocate command can be used for this. See #561.
• WP-CLI: Add an external configuration for WP-CLI so that a locally installed copy can be used outside of the VM. See #564.

VVV 1.2.0

1.2.0 Release Writeup

Changes:

• VVV is now MIT Licensed.
• _Possible Breaking:_ By default, database files are no longer mapped to a local location.
  • A full vagrant destroy and the removal of MySQL data from {vvv-dir}/database/data/ is recommended.
  • If database files already exist from an earlier version of VVV, data will continue to be mapped locally until removed.
  • Database data will continue to exist on the virtual machine through vagrant halt and vagrant suspend.
  • Database data will no longer exist on the virtual machine after vagrant destroy.
  • A db_backup script is provided by default that creates local backups of each database on halt, suspend, and destroy if the vagrant-triggers plugin is installed.
• _Possible Breaking:_ Ubuntu has been upgraded from 12.04 LTS to 14.04 LTS. We have also moved from 32bit to 64bit.
  • A full vagrant destroy is recommended for best results.
  • A new box will be downloaded for the base virtual machine. If you'd like to free space, remove the old box with vagrant box remove precise32. Running vagrant box list will show you all base VMs on your local machine.
  • With a new operating system comes a new RSA key. If you are connecting via SSH through an application that relies on your machines known_hosts file, you will need to clear the old key for 192.168.50.4. See #365
• Init scripts are now fired with source rather than bash. Due to this change, something like cd "$(dirname $0)" no longer works as expected. See #373 and #370 for reasoning and discussion.
• WordPress: Add develop_git to convert the default SVN checkout to Git.
• PHP: Update to PHP 5.5.x
• PHP: Remove php-apc and apc.ini. Enable built in opcache.
• PHP: Start tracking custom php5-fpm.conf file.
• PHP: Start tracking custom opcache.ini file.
• PHP: Update to PHPUnit 4.0.x
• PHP: Install XDebug PECL extension directly, rather than via apt.
• phpMyAdmin: Update to 4.2.13.1
• WP-Cli: Add support for autocomplete.
• VVV Dashboard: Add Opcache Status for opcache monitoring.
• Bash: Allow for a custom bash_prompt file in config/
• NodeJS: Use recommended PPAs to install
• NodeJS: Self update NPM during provisioning
• Logs: Map a shared directory for logs, start storing php_errors.log
• Nginx: Install using the mainline repository, currently 1.7.x.

VVV v1.1

Tag v1.1 for release