Date Fri 22 June 2012

I just finished up my first [Juju](https://juju.ubuntu.com/) charm, designed to deploy the tiny and not-yet-useful [libdep-service](https://launchpad.net/libdep-service/), which is going to become a micro-service used by [pkgme-service](https://launchpad.net/pkgme-service), which exists to automatically package submissions by application developers to [developer.ubuntu.com](http://developer.ubuntu.com/).

The charm works, insofar as it brings up a Django service that implements the API . It’s not really ready for others to use, as it doesn’t provide any interfaces and doesn’t make good use of Juju’s configuration system.

It’s very early days for me as a Juju user. The notes below are largely about problems, but I’m actually fairly optimistic that having a charm for my service will be very useful. Two big benefits so far:

EC2 2. I can deploy to LXC on my laptop, which means a fast, clean, local, production-like environment Anyway, on with the notes. 1. There’s less code than in my equivalent fabric task for deploying to2. I can deploy toon my laptop, which means a fast, clean, local, production-like environment