Charm needed: Django (framework)

[Adnane Belmadiaf]

A framework formula to deploy a django application in an ensemble.

[David Planella (dpm)]

There is some work on this already on http://micknelson.wordpress.com/2011/11/22/a-generic-juju-charm-for-django-apps/, but after talking to Michael, it seems it still needs some work. There is a list of unresolved issues and questions to complete the charm.

Any takers?

[Mark Mims (mark-mims)]

noodles, this is great work... do you mind if I put this up for review?

[Michael Nelson (michael.nelson)]

Hi Mark. I haven't had a chance to work on it since that branch/blog post, and tehre are a number of issues that need attention in the blog-post. If you've got ways to solve those, great!

[Juan L. Negron (negronjl)]

This is pretty good. I do have some feedback:
- The charm should provide something ( maybe http? )
- You should provide a README file ( http://jujucharms.com/charms/precise/mongodb is a somewhat good ) that explain the purpose of your charm as well as how to use it.

The above are very minimal changes that we need in order to approve the charm but, all in all, this is a very cool charm. I would encourage you to fix the small things detailed above before we can move forward with this.

-Juan

[Patrick Hetu (patrick-hetu)]

Since Django is using the wsgi protocol it would not be better to have a minimal django charm that requires
a wsgi subordinate charm that could be provided by charms like apache, nginx, gunicorn,etc ?

[Patrick Hetu (patrick-hetu)]

I've linked the branch of what I added in mind but I've not done any test on it yet. Also, this is what I had in mind for a wsgi subordinate:

http://bazaar.launchpad.net/~patrick-hetu/+junk/gunicorn-subordinate/files

[Marc Cluet (lynxman)]

Hi Patrick, I've been reviewing the charm and looks pretty good, I have just a couple remarks.

- There's two branches linked to the bug, could you make sure the one that is the final one is the only one linked? I've taken lp:~patrick-hetu/+junk/python-django just to be safe, if there's more than one charm a new bug needs to be created

- Please add the maintainer: field in metadata.yaml to appoint yourself as maintainer of this charm

As soon as those changes are done could you please change the state to "New" so I can review the charm again?

Thanks!

[Patrick Hetu (patrick-hetu)]

FYI I've create a new ticket: https://bugs.launchpad.net/charms/+bug/1012942