Ask HN: Large Django Application Design

We are trying to build an "enterprise" application with Django 1.4. This will be an application that may be both SaaS and custom install, and as previous incarnations (in PHP/ZF) have struggled with both process management (business) and technological constraints (stemming from same, as well as bad code begetting bad code), I am looking to see "how to do it right".

By this I mean, amongst other things, what are good "large" Django applications? What blogs and documentation provide good best practices? I know The Django Book is being actively worked on, but is currently quite dated.

I want to be able to figure out (as best as possible - the application will of course be organic and evolve, and I want a balance between "future-proof" and over-engineered YAGNI code) a lot of the questions that, together, will aid the construction of a good bedrock for an application, things like "how best to manage application configuration", "module structure" and the like.

How about me? Consider me someone who is diving in head-first, for better or worse, with substantial experience with the existing codebase, who suggested the rewrite, and who feels ninety per cent of the way there, and is in search of some "glue", moreso than a "magic recipe".

Effectively, in a single question: if you have worked on a large scale Django application (and for now, Django it is, though I have certainly explored Flask and others), what is the sage advice you'd give someone who needs to plan, and do, the same, to increase the chance of success?