docker-django-example VS gunicorn

Congrats on the release to the Django community!

If anyone is curious, I updated my Django / Docker starter kit app to use Django 5.0 at: https://github.com/nickjj/docker-django-example

It pulls together gunicorn, Celery, Redis, Postgres, esbuild and Tailwind with Docker Compose. It's set up to run in both development and production.

- https://github.com/nickjj/docker-django-example

For example I edit the regular non-lock file and then run ./run pip3:install from my host which handles the above. A repo with an example Django project in Docker can be found here https://github.com/nickjj/docker-django-example. There's a pip3-install script in the bin/ directory, you can replace that with Poetry commands instead.

Currently, I'm using a modified version of this Docker setup (https://github.com/nickjj/docker-django-example) to work locally and build/deploy a production image. However, using PyCharm as my IDE, the development process is incredibly slow, especially when adding or removing Python packages. It takes at least 3 minutes to rebuild the Docker image after adding a package, and PyCharm has to update its index. Additionally, PyCharm's inspector sometimes gets confused about which packages are already installed based on the requirements.txt.

If anyone is interested I updated my Django / Docker starter project for 4.2: https://github.com/nickjj/docker-django-example

Lots of handy stuff in this Django and Docker example project https://github.com/nickjj/docker-django-example He does a good course about Docker too.

If you're using Docker with a Debian based image you only need to apt install libpq-dev and you're good to go, it only needs to exist in your Docker image not your VPS directly. I've been using it for years. Here's a working example if you want to poke around https://github.com/nickjj/docker-django-example.

On a positive note, I would recommend perhaps looking at https://github.com/nickjj/docker-django-example for a good, somewhat beginner guide for django + docker work.

I put together https://github.com/nickjj/docker-django-example which pulls together a typical Django set up using Gunicorn, Celery, Postgres, Redis, esbuild and Tailwind.

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.