|
|
|
|
|
|
by oliwarner
3813 days ago
|
|
|
The Django docs aren't a bad place to start for first time deployments. The problem is there are architectural decisions to be made. I think anybody sane would recommend a virtualenv for all but the smallest projects (unikernel deployments) but what WSGI server? UWSGI's emperor mode is awesome for many sites but is another layer of configuration. UWSGI (sans emperor) and Gunicorn are both good point and shoot. Both need keeping alive (eg systemd). Once you've picked your WSGI server, read its documentation and try deploying. It's usually about then when you realise the other server might be better for you, or why storing your configuration in a database might make more sense. There are limitless choices here that are only apparent to the person behind the project. As for updating, that's more about automated testing and having a staging server (VM) to test on than any secret sauce. It's hard to do well manually. |
|
|
Yeah, uwsgi is where it's at. Even serves static files, so it's possible you won't even need nginx.
On updating I think:
1. remove from load balancer 2. update/upgrade/restart (hopefully it's already tested) 3. readd to load balancer