Notes on upgrading to 0.4.x - GetValkyrie/valkyrie GitHub Wiki

The 0.4.x branch introduces some significant changes. Among them:

• moving from Puppet to Ansible
• ditching vagrant-triggers, in favour of custom faux-plugins
• adding our own drushrc include file ~/.vagrant.drushrc.php
• moving to git submodules rather than sub-tree
• renaming the VM

The last two may require some manual steps to upgrade properly:

• drushrc include: Rather than re-writing ~/.drushrc.php regularly, we now add an include line that points to our custom drushrc file. This will minimize the impact on users who use custom settings. Since, prior to 0.4.x, we used to write alias search paths directly in ~/.drushrc.php, these will likely need to be manually removed.
• git submodules: When cloning the Valkyrie repo, you should now add '--recursive', in order to also clone all the submodules. For an existing install, this can be done by running: git submodule update --init --recursive
• new VM name: We changed the name of the VM from 'default' to 'valkyrie', so that when provisioning and such, we get the '==> valkyrie' prefix, among other things. Updating an existing project may result in Vagrant losing sight of an existing VM. However, it can still be accessed using its unique ID. The easiest way to find this is with the 'vagrant global-status' command.