The Django docs aren&#x27;t a bad place to start for first time deployments. The problem is there are architectural decisions to be made.<p>I think anybody sane would recommend a virtualenv for all but the smallest projects (unikernel deployments) but what  WSGI server? UWSGI&#x27;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).<p>Once you&#x27;ve picked your WSGI server, read <i>its</i> documentation and try deploying. It&#x27;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.<p>As for updating, that&#x27;s more about automated testing and having a staging server (VM) to test on than any secret sauce. It&#x27;s hard to do well manually.