title: Is it possible to maintain a reusable django *project* across apps?
body: <p>I'm trying to decide whether underneath 'reusable apps' it is doable to maintain a reusable bare project setup as well.</p>
  
  <p>On a side note: I can destroy any of my servers and rebuild it in barely hours as long as I have a (data) backup and a blueprint (in my case saltstack, but it might just as well be puppet, chef or what not).</p>
  
  <p>With a flexible infra, these deployment steps are next:</p>
  
  <ul>
  <li>Create  a virtualenv for the django application</li>
  <li>Check out my project (always named project)</li>
  <li>My project has a setup.py included. This sets the surroundings:
  <ul>
  <li>render settings files based on yaml data and templates</li>
  <li>Possibly loads fixtures when needed</li>
  <li>When in production, it renders apache config</li>
  <li>etc</li>
  </ul></li>
  <li>After that, as git submodules, you can plug your reusable apps to end up with a running webapplication.</li>
  </ul>
  
  <p>With quite a lot of intelligency built in the bare project base structure I ended up with my original question.</p>
  
  <p>I'm wondering if the project baseline is maintainable as a cross (Web)Application seperate git repo. Or does the project structure itself have to much specific moving parts related to the (Web)Application as a whole?</p>
  
  <p>E.g: pluggable apps go in INSTALLED_APPS, etc and always ending up with to much related/changing data.</p>
  
  <p>Hope it's clear. Looking forward to you comments</p>