search

meatballs / DjAxelrod

A repository to reproduce Axelrod's iterated prisoner's dilemma as a Django based web application.
MIT License
5 stars 4 forks source link

Use Nginx, and run django service as non-root user #14

Closed morlandi closed 9 years ago

morlandi commented 9 years ago

...

meatballs commented 9 years ago

Could you explain how this would be an improvement?

morlandi commented 9 years ago

While we download the full provisioning and build a VM for local testing, runserver is OK; however, with a little effort we could move toward a solution more suitable for deployment on a production server. Nginx would handle concurrent requests, and serve all static files (for example all bitmaps produced by each tournament) very efficiently with no need to involve Django; gunicorn would also be required to run Django as a WSGI application . It'a a fairly common Django setup for a production server

meatballs commented 9 years ago

I can see that would all be necessary for production. If we host at heroku, for example, that's precisely what we'd get. I can't see what we would gain by changing anything now, however. runserver is perfectly fine for our dev vm and our code would be fine at heroku.

morlandi commented 9 years ago

I understand your point of view; let's close this issue now and we might rediscuss it later on, when ready for the deployment of a working instance, which in my opinion would be necessary to share tornaments' results among people

meatballs commented 9 years ago

OK - A public instance is definitely required!! I'd like to get this up on heroku as quickly as we can. i just don't think we're quite ready yet.