Vagrant & Puppet Django Template
A PuppetVagrant configuration for a Django-centric machine at theTeam, utilising Puppet manifests for provisioning.
The aim is to have a single way of provisioning both local virtual development environments using Vagrant & Virtualbox while also at the same time building in such a way that the same Puppet manifests can be used to provision the staging & production Amazon EC2 environments.
The project should be able to be replicated on a per-machine basis to best work with the needs of a digital agency, and therefore should be as reusable as possible.
About & Current Status
Under development by the theTeam, London, this project is currently still at an experimental phase and as such shoud not be used in production.
The various modules are currently suited to our needs and our needs only but this could change with future development. If you wish to use it, you will most likely be best off forking the project and tailing it to your own requirements; if however you're after a box per the spec below - this will get you going with a working Django environment very quickly.
Distro: Ubuntu Server 10.04 LTS.
Web Servers: Nginx fronting Apache2.
#TODO in more detail.
Installation & Usage
1) Build a local Vagrant development box
Requirements: Vagrant & Virtualbox 4.x. So for Vagrant (it's a Ruby gem):
$ gem install vagrant
or, if you're using RVM (if not, why not?):
$ rvm 1.9.2 gem install vagrant
This will install the vagrant gem and it's dependencies.
Then checkout this project and put it somewhere, remembering the path to the modules directory.:
$ git clone git://github.com/theteam/vagrant-django-template.git
You will then need to set an environment variable to the vagrant-django-template home called VDT_HOME. In Linux this can be done as follows (put it in your bashrc or bash_profile for persistence)::
$ export VDT_HOME=$HOME/src/vagrant-django-template
2) Build an Amazon EC2 instance
With Thanks to
We have taken inspiration and teachings from various parts of the web in building this, here are just a few of the resources we used to pull this together: