title: Best practice for Django project working directory structure
body: <p>I know there is actually no single right way. However I've found that it's hard to create a directory structure that works well and remain clean for every developer and administrator. There is some standard structure in most projects on github. But it does not show a way to organize another files and all projects on pc.</p>
  
  <p>What is the most convenient way to organize all these directories on development machine? How do you name them, and how do you connect and deploy this to server?</p>
  
  <ul>
  <li>projects (all projects that your are working on)</li>
  <li>source files (the application itself)</li>
  <li>working copy of repository (I use git)</li>
  <li>virtual environment (I prefer to place this near the project)</li>
  <li>static root (for compiled static files)</li>
  <li>media root (for uploaded media files)</li>
  <li>README</li>
  <li>LICENSE</li>
  <li>documents</li>
  <li>sketches</li>
  <li>examples (an example project that uses the application provided by this project)</li>
  <li>database (in case sqlite is used)</li>
  <li>anything else that you usually need for successful work on project</li>
  </ul>
  
  <p>The problems that I want to solve:</p>
  
  <ul>
  <li>Good names of directories so that their purpose is clear.</li>
  <li>Keeping all project files (including virtualenv) in one place, so I can easily copy, move, archive, remove whole project or estimate disk space usage.</li>
  <li>Creating multiple copies of some selected file sets such as entire application, repository or virtualenv, while keeping single copy of another files that I don't want to clone.</li>
  <li>Deploying right set of files to the server simply by rsyncing selected one dir.</li>
  </ul>