How do you organize the code in your Django project?
26th September 2012
My answer to How do you organize the code in your Django project? on Quora
For http://lanyrd.com/ our layout looks something like this:
lanyrd/—parent directory, this is our root git repository
requirements.txt—our pip requirements file
app1/
app2/
app3/
management/
commands/—commands related to a specific app live inside that app
homepage/—one of our apps is responsible for our homepage
common/—some common code for the whole site, e.g. custom middleware
configs/
urls.py—our main URLs module
common_settings.py—settings common between dev and production
dev/
settings.py—our dev settings
manage.py—the manage.py script we use in dev
static/—our static assets
css/
js/
img/
templates/
base.html
homepage.html
app1/—templates relating to individual apps
app2/
app3/
We have a separate repository called “deploy” which contains our puppet recipes, our production settings and .tar.gz files for each of our pip requirements (since we don’t like our deploys to depend on files on the internet that might 404 some day).
I hope that’s helpful—let me know if you have any questions.
More recent articles
- Claude Opus 4.5, and why evaluating new LLMs is increasingly difficult - 24th November 2025
- sqlite-utils 4.0a1 has several (minor) backwards incompatible changes - 24th November 2025
- Olmo 3 is a fully open LLM - 22nd November 2025