Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Disclaimer: I'm a web developer for Mozilla!

Note that Playdoh is more specific to Mozilla websites than it should be, specifically around L10n, how it loads libraries, and deployment. It's also not being as actively maintained as it used to be. The big win for us is that it conforms to some requirements we had around deploying Django apps, and makes security reviews on our sites go a lot quicker.

It has some really cool libraries included, like jingo, useful middlewares in commonware, bleach, django-browserid(I maintain this!) and django-waffle.

IMO at the least it's an example of how a production Django application looks (something I appreciated when I was first learning Django) and is worth a look through the code.



> Note that Playdoh is more specific to Mozilla websites than it should be

True that. But with some work, this has the potential to be one of the best go-to templates for production Django webapps

Disclaimer: I'm a Mozillian.


Indeed, although I honestly have no experience with other templates similar to Playdoh (although I know they exist).

In my dream world, Playdoh is a Django project template (rather than this installable-as-command stuff that happened before Django had project template support) that makes it easy to enabled/disable certain annoying aspects, like Mozilla-like L10n. It'd get rid of the vendor submodules and load everything in via pip requirements (Erik Rose's peep would be super-helpful here to avoid having to run a PyPI mirror). It'd also get rid of a lot of the old not-commonly-used code, like the pre-commander deploy script, and it'd take away or make optional some of the extra libraries that not everyone uses (django-waffle is amazing but there's no point in loading it if you're not using it).


It looks great. I wonder, with availability of project templates 1.4 onwards, how would this be seen.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: