title: How to deploy a Django/Tornado based web app that's built with platter?
body: <p>This question is mostly about the technical details + some best practices of how to efficiently deploy a python web app that's built using platter.</p>
  
  <p>Taking Django for instance, I have a project that's already built into a tarball distribution. This includes all wheels of all deps + the package of the app itself.</p>
  
  <p>My repo directory also contains some other files that need to be distributed with the deployed code, such as: <code>manage.py</code>, a <code>fabfile</code> package with fabric utils, and some configuration files (for supervisor, nginx, etc).</p>
  
  <p>So my questions are:</p>
  
  <ol>
  <li>How can I wrap these extra files into the distribution that contains the project?</li>
  <li>If I simply use git to clone/pull the project on the server I have these files, but then I have duplicate of the source code being both in the project and zipped in the tarball. How can I avoid that? Committing the tarball into a separate repo?</li>
  <li>Perhaps the duplication is not so bad, and I'll end up with multiple tarballs in my <code>dist/</code> directory and only one symlinked to the <code>current</code> from which I deploy?</li>
  </ol>
  
  <p>Same goes for a Tornado based app.</p>