File	Date	Author	Commit
manifests	2013-04-03	Dave Brondsema	[eeb743] Revert "[#5973] crazy pysvn hacking so that pac...
README	2013-03-19	Dave Brondsema	<Commit 1baf650e208ce4a017e1d62d21a486e131b59d8b> [#5973] update vagrant scripts
Vagrantfile	2013-03-19	Dave Brondsema	<Commit 1baf650e208ce4a017e1d62d21a486e131b59d8b> [#5973] update vagrant scripts
Vagrantfile.pkg	2012-07-18	Tim Van Steenburgh	<Commit c0c52d558c403c21370cf72f917140e05eb94e08> Merge branch 'dev' of git://sfi-engr-scm-1/forg...
allura_setup.sh	2013-03-19	Dave Brondsema	<Commit 1baf650e208ce4a017e1d62d21a486e131b59d8b> [#5973] update vagrant scripts
start_allura	2013-03-19	Dave Brondsema	<Commit 1baf650e208ce4a017e1d62d21a486e131b59d8b> [#5973] update vagrant scripts

Read Me

To build an Allura vagrant box:

$ mkdir ~/vagrant_allura && cd ~/vagrant_allura

# Get the base box, see http://www.vagrantbox.es/
# 12.04 is LTS, so will be good to stick with for some time
$ vagrant box add ubuntu-1204-server-amd64 http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-vagrant-amd64-disk1.box
$ vagrant init ubuntu-1204-server-amd64

# Get a copy of the provisioning scripts (note, Vagrantfile may change from release to release and may need manual updating)
$ cp -R /var/local/allura/vagrant/* .

# At this point you can make whatever changes you want to the provisioning
# scripts.  Currently, the .pp puppet file runs first and sets some stuff up
# and then allura_setup.sh runs and does more.

# Provision the box (this will take a while)
$ vagrant up

# If you get an error, you can run `vagrant ssh` to get in and debug, and then `vagrant destroy` to start over

# Package the Allura box
$ vagrant package --vagrantfile Vagrantfile.pkg

# Test your new box
$ mkdir ~/vagrant_allura_test && cd ~/vagrant_allura_test
$ vagrant box add allura ~/vagrant_allura/package.box
$ vagrant init allura
$ vagrant up
$ vagrant ssh

# Do whatever testing you want...

# If everything checks out, you can rename your package.box and upload it