I am a complete newbie when it comes to sysadmin / deployment. Here is what I hope to do:
- The .com domain will be a regular WordPress site.
- Have either domain.com/app or app.domain.com, like Django webapp.
- Hosting on Linode.
- Fast and easy Django web server code updates.
From what I can tell, gunicorn is an elegant way to serve Django webapp, while WordPress works most naturally with Apache. Meanwhile, nginx is recommended as a proxy in front of killer weapons, and also appears to be used to improve WordPress site performance.
So, I think: use nginx as a proxy server that routes all incoming web requests to either gunicorn (for Django wepapp) or Apache (for the WordPress site). The Linode host will run nginx, gunicorn, and Apache at the same time.
Meanwhile, for Django webapp updates, I can just upgrade to the latest version of the code via github.
Does all this make sense? Do I even understand things conceptually right? Or bark the wrong tree? (For example, can / I use one Apache server to route requests to WordPress or a URL-based Django application?) What problems and issues should I consider when I examine how this works well and smoothly?
UPDATE : I did all this with (1) using Heroku to host my Django application, (2) using a CNAME record to map app.domain.com to Heroku -hosted Django application and (3) leave (for now) the site WordPress on its existing domain.com host. Fortunately, after gaining a lot of respect for what the system administrators and db administrators are doing, when I examined all this, now I can return to coding!
source share