Vagrant Testing

Starting the VM

You can test the provisioning/deployment using Vagrant. This requires Vagrant 1.7+. The Vagrantfile is configured to install the Salt Master and Minion inside the VM once you’ve run vagrant up. The box will be installed if you don’t have it already.:

vagrant up

The general provision workflow is the same as in the previous provisioning guide so here are notes of the Vagrant specifics.

Provisioning the VM

Set your environment variables and secrets in conf/pillar/local.sls. It is OK for this to be checked into version control because it can only be used on the developer’s local machine. To finalize the provisioning you simply need to run:

fab vagrant setup_master
fab vagrant setup_minion:salt-master,db-master,cache,web,balancer -H
fab vagrant deploy

The above command will setup Vagrant to run the full stack. If you want to test only a subset of the roles you can remove the unneeded roles. If you want to test the Celery setup then you can also add the queue and worker roles to the list.

The Vagrant box will use the current working copy of the project and the settings. If you want to use this for development/testing it is helpful to change your local settings to extend from staging instead of dev:

# Example
from school_navigator.settings.staging import *

# Override settings here
DATABASES['default']['NAME'] = 'school_navigator_local'
DATABASES['default']['USER'] = 'school_navigator_local'

DEBUG = True

This won’t have the same nice features of the development server such as auto-reloading but it will run with a stack which is much closer to the production environment. Also beware that while conf/pillar/local.sls is checked into version control, generally isn’t, so it will be up to you to keep them in sync.

Testing on the VM

With the VM fully provisioned and deployed, you can access the VM at the IP address specified in the Vagrantfile, which is by default. Since the Nginx configuration will only listen for the domain name in conf/pillar/local.sls, you will need to modify your /etc/hosts configuration to view it at one of those IP addresses. I recommend, otherwise the ports in the localhost URL cause the CSRF middleware to complain REASON_BAD_REFERER when testing over SSL. You will need to add: <domain>

where <domain> matches the domain in conf/pillar/local.sls. For example, let’s use

In your browser you can now view and see the VM running the full web stack.

Note that this /etc/hosts entry will prevent you from accessing the true When your testing is complete, you should remove or comment out this entry.