Derek Stegelman

Django Boilerplate

Lately, I've been needing a starting place for my django projects, and I've noticed a common pattern.

  • Too many applications floating around that get confused with other module directories.
  • A need for separate urls and settings files for production, testing, and staging.
  • A place to keep custom libraries that aren't shared.
  • Proper inheritance of settings.
  • Api management for apps that need APIs.
  • Reusable fabric files and automation of compression and build scripting.

On top of this one of my reoccuring problems has been the need to look up what should be basic stuff out of the Django docs, ie, how to import render, or how to setup a RSS feed. What I've started on github, and what I've been working on at work as well is a boiler plate of sorts. A way to get my projects quickly up to speed by automating and simplifying some redundant tasks. In the boilerplate you'll find a Django static server, sqlite, and a fabfile already to go. You'll also notice some libraries that I use a lot, and snippets that I typically need have been complied into a pip installable library on github as well.