title: How to deploy a Django to the production server without mercurial files?
body: <p>I am originally a .NET developer and back then when we had to release a software from Visual Studio, we had to switch it to release mode to make sure the debug hooks are removed and the repository files are left behind. The end result was a clean set of files ready to be pushed into production.</p>
  
  <p>After switching to Django and working with it for nearly three months I am now ready to deploy the first app. I have done quite some reading on it. I know how to set the debug to False and having a production_setting.py and how to deploy with WSGI on Apache.</p>
  
  <p>But something I still haven't figured out is a nice process to push out a release.</p>
  
  <p>With what I know now, I would do the following for a release:</p>
  
  <ul>
  <li>Copy all the files by hand to a upload directory (excluding hidden mercurial directories)</li>
  <li>Zip them all</li>
  <li>sending them over SCP to the Ubuntu server</li>
  <li>Logging into the server</li>
  <li>Extracting the zip file and putting everything into place</li>
  <li>Modifying the setting_production.py and enter the credentials</li>
  </ul>
  
  <p>Is this a healthy process for Django deployment? :)<br>
  FYI I am using Aptana Studio 3.2.1</p>
  
  <p>Thanks for any tips</p>