This repo contains the Ansible config to build a Clojars server from scratch. It includes a Vagrantfile for running and testing locally.

Install Virtualbox, Vagrant 1.8, and Ansible 2.0.0. To install Ansible 2 on Homebrew, run brew install ansible --devel as it hasn't been officially released yet.

You must have Jinja 2.8 or higher installed. Depending on your platform, Jinja 2.7 or lower may be installed by the system. Check with pip show jinja2. Homebrew will install the right versions, I'm not so sure about other platforms. To install Jinja2, run pip install jinja2 or pip install --upgrade https://pypi.python.org/packages/source/J/Jinja2/Jinja2-2.8.tar.gz (perhaps with sudo). As is quite obvious from this rambling paragraph, some guidance from a Python expert on the correct process here would be very helpful.

Run vagrant up to start up the VM. Before you go any further, run vagrant snapshot save clean-build. This will save a snapshot of our VM and allow us to reset our VM state quickly.

Installing Java and updating the apt-cache is the slowest operation in the ansible playbook. You may want to run

ansible-playbook \
   --inventory local --private-key=.vagrant/machines/default/virtualbox/private_key \
   --user vagrant \
   java.yml

before snapshotting to speed up rebuilds.

To test everything is working, run:

ansible all -m ping --inventory local --private-key=.vagrant/machines/default/virtualbox/private_key -u vagrant

You should see

127.0.0.1 | SUCCESS => {
    "changed": false,
    "ping": "pong"
}

There is some config for Clojars which is sensitive and cannot be publicly shared in the Github repo. This is placed in private/vars.yml. For development purposes, private/vars.yml.example is a vars file which looks like the real one but with sensitive information replaced. Run cp private/vars.yml.example private/vars.yml to create your private vars file.

Run:

ansible-playbook -i local --private-key=.vagrant/machines/default/virtualbox/private_key -u vagrant site.yml

To restore your vm (I do this every few hours to make sure things haven't drifted too far)

vagrant snapshot restore clean-build

• Follow Ansible best practices
• Add an {{ ansible_managed }} comment in the header of all templates and files
• Place any private files in private/

To print manually installed packages:

cat /var/log/apt/history.log ) | egrep '^(Start-Date:|Commandline:)' | grep -v aptdaemon | egrep -B1 '^Commandline:'

Distributed under the Eclipse Public License. See the file COPYING.