2.2.1

Fixed

• Fixed a where https provisioning failed for Vagrantfiles with multiple extra_hostnames

2.2.0

Fixed

• Fixed a bug where quoted drush arguments (e.g. passwords with spaces, SQL queries, PHP statements) were passed to drush incorrectly (issue #36, PR #53)

Changed

• HTTPS is now enabled by default (PR #49)
• The self-signed certificate generation now uses a configuration template, which includes a subjectAltName (issue #50, PR #51
• The templated Vagrantfile now requires Vagrant >= 2.1.0 (issue #52, PR #54)

Updating from 2.1.0

• This update does not require destroying your current vagrant box.
• These steps apply for projects that have not copied the full set of provisioning into their project; if there is a provisioning/ directory in your project root, you may not receive the full set of fixes with these steps alone.

1. Uninstall the vagrant-triggers plugin with vagrant plugin uninstall vagrant-triggers
2. Update to Vagrant >= 2.1.0
3. In your project, require this new release of the-vagrant
4. In your project, run vendor/bin/the-vagrant-installer
5. Respond to the prompts to regenerate your Vagrantfile
6. Review the changes to make sure that you don't lose any customizations you had to this file
7. Run vagrant up --provision or vagrant reload --provision to update your box

2.2.0-alpha2

Fixed since 2.2.0-alpha

• Fixed issue with san.cnf template that prevented certificate generation

2.2.0-alpha

(see 2.2.0 release notes)

2.1.0

Changes

• Now requires version >= 1.2.0, < 2.0 of the drupalbox, instead of allowing v1.1.1. See palantir/drupalbox on Vagrant Cloud for the box changelogs.
• Removed VMware support for the >1.2.0 drupalbox
• Find drushrc.php in a project's drush/ directory as well as in the conf/ directory

Fixes

• Updated README
• Removed debug message from provisioning
• Removed duplicate solr flag setting in the Vagrantfile template

Updating from 2.0.1

After updating to this release:

1. Review your Vagrantfile and verify that there is only one copy of the solr configuration line (see 682fad)
2. In your project, run vagrant box update to ensure that you have the 1.2.0 version of the drupalbox Vagrant base box. If this downloads a new box, you will need to destroy and re-create your box:
   1. vagrant destroy
   2. vagrant up
3. Otherwise, if you are already using drupalbox v1.2.0, you may re-provision vagrant up --provision or vagrant reload --provision to apply the drushrc.php changes

2.0.1

Changes

• Fixed provisioning failures in some cases when a .zshrc file is missing
• Updates the Solr management role for the Drupalbox 1.1.1 release of the VM
• Sets the post_max_size in addition to the upload_max_filesize in php.ini

Updating from 2.0.0

If have been using the-vagrant version 2.0.0, and you would like to enable Solr on the box for your project, you will need to:

1. Destroy your current vagrant box: vagrant destroy (this will wipe all of your drupal databases)
2. Download the latest version of the drupalbox vagrant box: vagrant box update --box palantir/drupalbox. After running this you should have at least version 1.1.1 of this box.
3. Update palantirnet/the-vagrant in your project: composer update palantirnet/the-vagrant
4. Edit your vagrantfile and make sure that it contains ansible_solr_enabled = true
5. Start your vagrant: vagrant up
6. Solr will now be available at http://yoursite.local:8983/solr and your site can use either the drupal7 or drupal8 core.

2.0.0 - PHP 7 box

Changes

Updates to the palantir/drupalbox release v1.1.0, which supports PHP 7.

Updating existing installations

If you update from the 1.x branch of this project, you will need to destroy and re-create your Vagrant box:

vagrant destroy
vagrant up

• If you have customized the ansible_system_packages variable in your Vagrantfile, make sure it doesn't contain packages that are specific to PHP 5 (e.g. LDAP)
• If you are using Solr on your box, you'll need to temporarily disable it (by setting ansible_solr_enabled = false in your Vagrantfile) until the v1.1.1 release of the drupalbox

Project changes

The v0.x releases of the drupalbox, and PHP 5, are supported in the release-1.x branch.

1.1.1

Fixes the issue where the Vagrant ansible provisioner was not happy when an additional playbook was not used:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

ansible remote provisioner:

• playbook file path must be set.

carrot cake

New Features

• Allow using a project-specific ansible playbook in addition to the playbook in the-vagrant.

construction-elevator

New Features

• HTTPS config

Fixes

• Changes the Apache user to vagrant to work around permissions limitations for NFS mounts