title: Django deployment with mod_wsgi and .htaccess
body: <p>Here is my set-up: Django 1.7; Python 3.4, mod_wsgi, virtualenv, apache2. Django and other pakages are installed after activating the virtualenv.</p>
  
  <p>Need .htaccess file for redirects. I am new to deployment world, so please bear with me. </p>
  
  <p>Here is what I have done so far:</p>
  
  <p>In the virtualhost, I call the wsgi.py file after specifying the path to site-package path for Django. This works fine, however I  have 2 questions:</p>
  
  <p>1) I saw a lot of sites which were calling the file.wsgi file from the virtualhost config, and in the .wsgi file they were calling the exec to activate the env and call django app. The Django guide however has a different approach (<a href="https://docs.djangoproject.com/en/1.8/howto/deployment/wsgi/modwsgi/" rel="nofollow">https://docs.djangoproject.com/en/1.8/howto/deployment/wsgi/modwsgi/</a>) and this is the one I implemented. Do I need a file.wsgi if I want to have htaccess deal with the request and then forward it to Django urls.py?</p>
  
  <p>2) If the set-up that I have is ok for deployment, where do i place the .htaccess file and ensure that apache sends the request to htaccess which in turn sends it to Django app?</p>
  
  <p>Thanks</p>