gunicorn autoreload on source change

Question

Finally I migrated my development env from runserver to gunicorn/nginx.

It\'d be convenient to replicate the autoreload feature of runserver to gunicorn, so the serv

Answer 1

One option would be to use the --max-requests to limit each spawned process to serving only one request by adding --max-requests 1 to the startup options. Every newly spawned process should see your code changes and in a development environment the extra startup time per request should be negligible.