3 ms·

I did a bare metal install, and I sadly don't recall what was painful about it specifically; I recall fighting with Apache and Nginx and WSGI in some sequence o

• JosephRedfern 11y ago
  In terms of fighting with Apache/Nginx/WSGI, I think you'd have similar issues with most other frameworks. During development, you can run a self-hosted Django instance with `python manage.py runserver`. Once you've developed your application and are ready to deploy, I'd personally suggest this guide (although others may have different opinions): http://uwsgi-docs.readthedocs.org/en/latest/tutorials/Django_and_nginx.html http://uwsgi-docs.readthedocs.org/en/latest/tutorials/Django.... It boils down to installing uwsgi, creating a wsgi config file (which specifies the path to your Django app, and it's name), and then telling nginx to proxy requests to your wsgi socket.
  • vessenes 11y ago
    It might be you're correct in general. The last few years, my team has worked with go fairly extensively for this sort of work, and it is a single line of go and a very short nginx block to get running. I think the difference was that django wanted python running through WSGI; the go servers expect to be running behind the scenes and just using nginx as a proxy.
• deleted 11y ago
  [deleted]