Agile Collective Parrot Install - agilecollective/parrot GitHub Wiki

At Agile Collective we have a few different and evolving needs in our local Vagrant based development boxes. Ideally we want to run from the https://github.com/computerminds/parrot repository, but until we can get the various options merged in, we will maintain our own working copy branch here.

Setup and install for the Agile Collective Vagrant users.

The master branch will track the Computer Minds master branch for now. The current working branch for Agile Collective developers is the branch called 'working'. See https://github.com/agilecollective/parrot/tree/working

Currently this adds a couple of things we use that are not yet in the parent repo: 1 - nodejs to support using gulp for our front end sass compilation. 2 - a missing php-mysql package that prevents an error when running drush inside the box.

Install steps

1 Clone the repo and check out the 'working' branch

git clone [email protected]:agilecollective/parrot.git
cd parrot
git checkout working

2 Create a config.yml

The config.yml page allows us to configure the vagrant box to our own ends. This is an example of the config.yml file I use:

sites: "/Users/finn/sites"
databases: "databases" 
memory: 2048
with_gui: false
ip: "192.168.50.4"
php_version: "5.6"
mysql_version: "5.5"
webroot_subdir: "/web"
box_name: "Parrot-Trusty"
varnish_enabled: true
gulp_enabled: true
ohmyzsh_enabled: false

Linux: On Linux Luke needed to add this to the config file in order to overcome an error "Error: Could not create user host_user: Execution of '/usr/sbin/useradd -g 1001 -u 1001 host_user' returned 4: useradd: UID 1001 is not unique":

local_user_uid: 1002

For details of each option in config.yml, see https://github.com/computerminds/parrot/wiki/Configuration Note: the only one that is not documented yet is the gulp_enabled. This installs nodejs and gulp, ready for sass compilation.

3 Vagrant Up!

vagrant up

This will take a while, but works for me without errors (OSX 10.10.5, Vagrant 1.8.5, Virtualbox 5.1.6).

4 Sites folder

I like to keep my sites and databases folder outside the Vagrant root, to allow me to run different Vagrant boxes with different setups, and avoid duplication of the sites folder. You can do this by specifying an absolute path to the folder rather than a relative path.

5 Databases

When destroying and rebuilding the Vagrant box, it is useful to run the great little script that dumps out all the databases ready for re-importing on a Vagrant up. The script should be run outside of the box from the Vagrant root, and is:

scripts/dump-databases.sh

See docs here: https://github.com/computerminds/parrot/wiki/Mysql-server