title: How to deploy a WordPress site and Django site on the same domain?
body: <p>I'm a complete newbie when it comes to sysadmin/deployment. Here's what I'm hoping to accomplish:</p>
  
  <ol>
  <li>Have domain.com be a normal WordPress site.</li>
  <li>Have either domain.com/app or app.domain.com be a Django webapp.</li>
  <li>Hosting on Linode.</li>
  <li>Quick and easy updates of the Django webapp code.</li>
  </ol>
  
  <p>From what I can tell, gunicorn is an elegant way to serve the Django webapp, while WordPress fits most naturally with Apache. Meanwhile, nginx is recommended as a proxy in front of gunicorn and also seems to be used to improve performance of WordPress sites. </p>
  
  <p>So what I'm thinking is: use nginx as a proxy server that routes all incoming web requests to either gunicorn (for the Django wepapp) or Apache (for the WordPress site). The Linode host would be running nginx, gunicorn, and Apache simultaneously.</p>
  
  <p>Meanwhile, for updates of the Django webapp, I can simply update to the latest version of the code via github.  </p>
  
  <p>Does all that make sense? Am I even understanding things conceptually correctly? Or barking up the wrong tree entirely? (For instance can/should I just use a single Apache server to route requests to either WordPress or the Django app based on URL?) What gotchas and issues should I keep in mind as I research how to get this running nice and smoothly?</p>
  
  <p><strong>UPDATE</strong>: I've side-stepped all of this by (1) using Heroku to host my Django app, (2) using a CNAME record to map app.domain.com to the Heroku-hosted Django app, and (3) leaving (for now) the WordPress site on its existing host at domain.com. Thankfully, after gaining great new respect for what sysadmins and db admins do as I investigated all this, now I can get back to coding!</p>