django-heroku VS gunicorn

Surprised nobody here has mentioned WhiteNoise yet. Use the django-heroku package and WhiteNoise and you can serve all your static files directly from Heroku, no need for S3. It's pretty much magic, just follow the installation instructions for django-heroku, it has WhiteNoise as a dependency. If you want better performance then stick a CDN like CloudFlare in front and it will take care of caching all the static files. Heroku themselves recommend using WhiteNoise, the django-heroku package just does all the config for you.

django-heroku: We have to Configure Django app for Heroku. This lib provides settings, logging and test runner configurations.

But I'm not sure the python version is the issue here. This issue looks similar to yours: https://github.com/heroku/django-heroku/issues/39

And Its from Heroku Docs, and last maintained 3 years ago..

You should probably avoid using the Django-Heroku package at this point. The last substantive code commit is nearing three years ago. So I would try removing the django_heroku.settings(locals()) line. You would also need to insert new settings to use PostgreSQL as your database. On Heroku, this is best accomplished with [dj-database-url](https://github.com/jacobian/dj-database-url), which was a dependency of Django-Heroku but is still updated. There are many ways to set it up, but I typically use:

I find it very peculiar that Heroku's own documentation suggest using django-heroku although the repository is in archive mode.

I'm hoping so – gunicorn has a long-open pull request that would fix `--reuse-port`, which currently does nothing

https://github.com/benoitc/gunicorn/pull/2938

However, I'm curious about the best way to deploy, specifically with regard to WSGI. I've tried using the raw eventlet WSGI server (`eventlet.wsgi.server(eventlet.listen(("", 8000)), application)`). I then start it with `python manage.py runserver`. This has worked okay, but I'm unsure about how scalable it is. It seems like the standard stack is Django + Gunicorn + NGINX. Based on `python-socketio` documentation, this should be possible. I tried django + eventlet + gunicorn, but it seems like gunicorn a) [doesn't play nice with eventlet](https://github.com/benoitc/gunicorn/pull/2581) and b) only supports one worker. Gevent + Gunicorn doesn't have this bug, but still only supports one worker. Also, I'm not sure how actively maintained gevent is. So I'm not sure how scalable either Gunicorn + eventlet or Gunicorn + geventlet is as a WSGI server. So I'm not sure if Gunicorn is my best bet, or if it's too limited.

For building your API, I recommend using the Flask library. It is very beginner-friendly, and you will be able to build a simple API in a matter of minutes! Keep in mind that, for a more serious project, you should definitely use something like gunicorn to run you API as a production server.

Interesting looks like it might actually be a python bug. Somehow just changing from sys.exit(0) -> os._exit(0) apparently fixes it.

https://github.com/benoitc/gunicorn/pull/2820

The cool thing is that you can easily migrate your WSGI- application such as Flask, Django, or Gunicorn to AWS.

Yeah, that's kind of the impression I was getting. I stumbled across a github issue for gunicorn along these lines.

Taking a glimpse at gunicorn's code it looks like they pretty much all do the same: 2. seems to be creating a wsgi app using django's internals, and 3. uses 2.