I&#39;m using a Docker container for Django development, and the container runs Gunicorn with Nginx. I&#39;d like code changes to auto-load, but the only way I can get them to load is by rebuilding with docker-compose (`docker-compose build`). The problem with &quot;build&quot; is that it re-runs all my pip installs. 

I&#39;m using the Gunicorn `--reload` flag, which is apparently supposed to do what I want. Here are my Docker config files:

    ## Dockerfile:
    FROM python:3.4.3
    RUN mkdir /code
    WORKDIR /code
    ADD . /code/
    RUN pip install -r /code/requirements/docker.txt
    
    ## docker-compose.yml:
    web:
      restart: always
      build: .
      expose:
        - &quot;8000&quot;
      links:
        - postgres:postgres
      volumes:
        - /usr/src/app/static
      env_file: .env
      command: /usr/local/bin/gunicorn myapp.wsgi:application -w 2 -b :8000 --reload
    
    nginx:
      restart: always
      build: ./config/nginx
      ports:
        - &quot;80:80&quot;
      volumes:
        - /www/static
      volumes_from:
        - web
      links:
        - web:web
    
    postgres:
      restart: always
      image: postgres:latest
      volumes:
        - /var/lib/postgresql
      ports:
        - &quot;5432:5432&quot;

I&#39;ve tried some of the other Docker commands (`docker-compose restart`, `docker-compose up`), but the code won&#39;t refresh.

What am I missing?


Auto-reloading of code changes with Django development in Docker with Gunicorn

With my Procfile like this:

    web: gunicorn app:app \
        --bind &quot;$HOST:$PORT&quot; \
        --debug --error-logfile &quot;-&quot; \
        --enable-stdio-inheritance \
        --reload \
        --log-level &quot;debug&quot; 

is it in any way possible to get python `print` statements to be logged to stdout / bash? I am using the `bottle` framework here as well, if that affects anything.


Is there a way to log python print statements in gunicorn?

A lot of Django app deployments over Amazon&#39;s EC2 use HTTP servers NGINX and Gunicorn. 

I was wondering what they actually do and why both are used in parallel. What is the purpose of running them both in parallel?

What is the purpose of NGINX and Gunicorn running in parallel?

The gunicorn documentation talks about editing the config files, but I have no idea where it is.

Probably a simple answer :) I&#39;m on Amazon Linux AMI.

Where is the Gunicorn config file?

I have web application written in Flask. As suggested by everyone, I can&#39;t use Flask in production. So I thought of **Gunicorn with Flask**.  

In Flask application I am loading some Machine Learning models. These are of size 8GB collectively. Concurrency of my web application can go upto **1000 requests**. And the RAM of machine is 15GB.  
So what is the best way to run this application?

How to run Flask with Gunicorn in multithreaded mode

I have setup gunicorn with 3 workers 30 worker connections and using eventlet worker class. It is setup behind Nginx. After every few requests, I see this in the logs.


    [ERROR] gunicorn.error: WORKER TIMEOUT (pid:23475)
    None
    [INFO] gunicorn.error: Booting worker with pid: 23514

Why is this happening? How can I figure out whats going wrong?

thanks

Gunicorn worker timeout error

I&#39;m building an app with Flask, but I don&#39;t know much about WSGI and it&#39;s HTTP base, Werkzeug. When I start serving a Flask application with gunicorn and 4 worker processes, does this mean that I can handle 4 concurrent requests?

I do mean concurrent requests, and not requests per second or anything else.

How many concurrent requests does a single Flask process receive?

Finally I migrated my development env from runserver to gunicorn/nginx.

It&#39;d be convenient to replicate the autoreload feature of runserver to gunicorn, so the server automatically restarts when source changes. Otherwise I have to restart the server manually with `kill -HUP`.


Any way to avoid the manual restart?

gunicorn autoreload on source change

I want to know what exactly it means when a web server describes itself as a pre-fork web server. I have a few examples such as [unicorn][1] for ruby and [gunicorn][2] for python.

More specifically, these are the questions:

- What problem does this model solve?
- What happens when a pre-fork web server is initially started?
- How does it handle requests?

Also, a more specific question for unicorn/gunicorn:

Let&#39;s say that I have a webapp that I want to run with (g)unicorn. On initialization, the webapp will do some initialization stuff (e.g. fill in additional database entries). If I configure (g)unicorn with multiple workers, will the initialization stuff be run multiple times?

  [1]: http://unicorn.bogomips.org/
  [2]: http://gunicorn.org/

What exactly is a pre-fork web server model?

In terms of Gunicorn, I am aware there are various worker classes but for this conversation I am just looking at the sync and async types.

From my understanding ...

    sync
    workers = (2 * cpu) + 1
    worker_class = sync
    
    async (gevent)
    workers = 1
    worker_class = gevent
    worker_connections = a value (lets say 2000)

So (based on a 4 core system) using sync workers I can have a maximum of 9 connections processing in parallel. With Async I can have up to 2000, with the caveats that come with async.

**Questions**

 - So where do threads fit in? Can I add threads to both the sync and
   async worker types? 
 - What is the best option around gunicorn workers?
   Should I wish to place gunicorn in front of a Django API, with the
   requirement of processing 100s of requests in parallel?
 - Are gevent and sync worker classes thread safe?



Gunicorn Workers and Threads

I have looked around for a while, and I was surprised not finding any information whether Gunicorn runs on Windows or not.
Does anyone know if that is the case, and if so, where can I find some documentation about it?

Does Gunicorn run on Windows

I want to run my django project under gunicorn on localhost. I installed and integrated gunicorn. When I run:

    python manage.py run_gunicorn

It works but there are no any static files (css and js)

I disabled debug and template_debug in settings.py (made them false), but it is still same.  Am I missing something?

I call statics like:

    {{ STATIC_URL }}css/etc....


How to make Django serve static files with Gunicorn?

I have a django app and trying to set it up with gunicorn first and later with supervisor and nginx.

The app is running with the normal django command perfectly like `python manage.py runserver`

I installed the gunicorn using pip like `pip install gunicorn` and django version is `1.5.3`

when i run the below command inside the virtual env like below

`gunicorn  hello.wsgi:application -b xx.xxx.xxx.xx:8000` and faced the error


    Traceback (most recent call last):
      File &quot;/root/Envs/proj/bin/gunicorn&quot;, line 9, in &lt;module&gt;
        load_entry_point(&#39;gunicorn==19.0.0&#39;, &#39;console_scripts&#39;, &#39;gunicorn&#39;)()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py&quot;, line 74, in run
        WSGIApplication(&quot;%(prog)s [OPTIONS] [APP_MODULE]&quot;).run()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/app/base.py&quot;, line 166, in run
        super(Application, self).run()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/app/base.py&quot;, line 71, in run
        Arbiter(self).run()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/arbiter.py&quot;, line 169, in run
        self.manage_workers()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/arbiter.py&quot;, line 477, in manage_workers
        self.spawn_workers()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/arbiter.py&quot;, line 537, in spawn_workers
        time.sleep(0.1 * random.random())
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/arbiter.py&quot;, line 209, in handle_chld
        self.reap_workers()
      File &quot;/root/Envs/proj/local/lib/python2.7/site-packages/gunicorn/arbiter.py&quot;, line 459, in reap_workers
        raise HaltServer(reason, self.WORKER_BOOT_ERROR)
    gunicorn.errors.HaltServer: &lt;HaltServer &#39;Worker failed to boot.&#39; 3&gt;

So why actually the above error is encountered and whats the fix ?

gunicorn.errors.HaltServer: &lt;HaltServer &#39;Worker failed to boot.&#39; 3&gt; django

This is a broad question but I&#39;d like to get a canonical answer. I have been trying to deploy a site using *gunicorn* and *nginx* in *Django*. After reading tons of tutorials I have been successful but I can&#39;t be sure that the steps I followed are good enough to run a site without problems or maybe there are better ways to do it. That uncertainty is annoying.

That&#39;s why I&#39;m looking for a very detailed and well explained answer for newbies. I don&#39;t want to explain too much what I know and what I don&#39;t know since this could skew the answers a bit and other people could benefit to a lesser degree from your answers. However, some things I&#39;d like to see mentioned are:

 - What &quot;setup&quot; have you seen work best? I used *virtualenv* and moved my *Django* project inside this environment, however I have seen another setups where there is a folder for virtual environments and other for projects.

 - How can I setup things in a way that allows several sites to be hosted in a single server?

 - Why some people suggest using `gunicorn_django -b 0.0.0.0:8000` and others suggest `gunicorn_django -b 127.0.0.1:8000`? I tested the latter in an Amazon EC2 instance but it didn&#39;t work while the former worked without problem.

 - What is the logic behind the config file of nginx? There are so many tutorials using drastically different configuration files that I&#39;m confused on which one is better. For example, some people use `alias /path/to/static/folder` and others `root /path/to/static/folder`. Maybe you can share your preferred configuration file.

 - Why do we create a symlink between `site-available` and `sites-enabled` in `/etc/nginx`?

 - Some best practices are as always welcomed :-)


Thanks

Deploying Django with gunicorn and nginx

I&#39;m installing a previously built website on a new server. I&#39;m not the original developer.

I&#39;ve used Gunicorn + nginx in the past to keep the app alive (basically following [this tutorial](https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-14-04)), but am having problems with it here.

I `source venv/bin/activate`, then `./manage.py runserver 0.0.0.0:8000` works well and everything is running as expected. I shut it down and run `gunicorn --bind 0.0.0.0:8000 myproject.wsgi:application`, and get the following:

    [2016-09-13 01:11:47 +0000] [15259] [INFO] Starting gunicorn 19.6.0
    [2016-09-13 01:11:47 +0000] [15259] [INFO] Listening at: http://0.0.0.0:8000 (15259)
    [2016-09-13 01:11:47 +0000] [15259] [INFO] Using worker: sync
    [2016-09-13 01:11:47 +0000] [15262] [INFO] Booting worker with pid: 15262
    [2016-09-13 01:11:47 +0000] [15262] [ERROR] Exception in worker process
    Traceback (most recent call last):
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/arbiter.py&quot;, line 557, in spawn_worker
        worker.init_process()
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/workers/base.py&quot;, line 126, in init_process
        self.load_wsgi()
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/workers/base.py&quot;, line 136, in load_wsgi
        self.wsgi = self.app.wsgi()
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/app/base.py&quot;, line 67, in wsgi
        self.callable = self.load()
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/app/wsgiapp.py&quot;, line 65, in load
        return self.load_wsgiapp()
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/app/wsgiapp.py&quot;, line 52, in load_wsgiapp
        return util.import_app(self.app_uri)
      File &quot;/var/www/myproject/venv/lib/python3.5/site-packages/gunicorn/util.py&quot;, line 357, in import_app
        __import__(module)
    ImportError: No module named &#39;myproject.wsgi&#39;
    [2016-09-13 01:11:47 +0000] [15262] [INFO] Worker exiting (pid: 15262)
    [2016-09-13 01:11:47 +0000] [15259] [INFO] Shutting down: Master
    [2016-09-13 01:11:47 +0000] [15259] [INFO] Reason: Worker failed to boot.

I believe it has something to do with the structure of the whole application. Before, I&#39;ve built apps with the basic structure of:

    myproject
    ├── manage.py
    ├── myproject
    │&#160;&#160; ├── urls.py
    │&#160;&#160; ├── views.py
    │&#160;&#160; ├── component1
    │   │&#160;&#160; ├── urls.py
    │   │&#160;&#160; └── views.py
    │&#160;&#160; ├── component2
    │   │&#160;&#160; ├── urls.py
    │   │&#160;&#160; └── views.py
    ├── venv
    │&#160;&#160; ├── bin
    │&#160;&#160; └── ...

This one, instead, has a structure like:

    myproject
    ├── apps
    │&#160;&#160; ├── blog
    │   │&#160;&#160; ├── urls.py
    │   │&#160;&#160; ├── views.py
    │&#160;&#160; │	  └── ...
    │&#160;&#160; ├── catalogue
    │   │&#160;&#160; ├── urls.py
    │   │&#160;&#160; ├── views.py
    │&#160;&#160; │	  └── ...
    │&#160;&#160; ├── checkout
    │   │&#160;&#160; ├── urls.py
    │   │&#160;&#160; ├── views.py
    │&#160;&#160; │	  └── ...
    │&#160;&#160; ├── core
    │   │&#160;&#160; ├── urls.py
    │   │&#160;&#160; ├── views.py
    │&#160;&#160; │	  └── ...
    │&#160;&#160; ├── customer
    │&#160;&#160; ├── dashboard
    │&#160;&#160; └──  __init__.py
    ├── __init__.py
    ├── manage.py
    ├── project_static
    │&#160;&#160; ├── assets
    │&#160;&#160; ├── bower_components
    │&#160;&#160; └── js
    ├── public
    │&#160;&#160; ├── emails
    │&#160;&#160; ├── media
    │&#160;&#160; └── static
    ├── settings
    │&#160;&#160; ├── base.py
    │&#160;&#160; ├── dev.py
    │&#160;&#160; ├── __init__.py
    │&#160;&#160; ├── local.py
    │&#160;&#160; └── production.py
    ├── templates
    │&#160;&#160; ├── base.html
    │&#160;&#160; ├── basket
    │&#160;&#160; ├── blog
    │&#160;&#160; └── ....
    ├── urls.py
    ├── venv
    │&#160;&#160; ├── bin
    │&#160;&#160; ├── include
    │&#160;&#160; ├── lib
    │&#160;&#160; ├── pip-selfcheck.json
    │&#160;&#160; └── share
    └── wsgi.py

So, there&#39;s no &#39;main&#39; module running the show, which is what I expect gunicorn is looking for.

Any thoughts?

**wsgi.py**:

    import os
    
    from django.core.wsgi import get_wsgi_application
    
    os.environ.setdefault(&quot;DJANGO_SETTINGS_MODULE&quot;, &quot;settings&quot;)
    
    application = get_wsgi_application()

Gunicorn, no module named &#39;myproject

I am running a **Flask/Gunicorn** Python app on a Heroku Cedar dyno. The app returns `JSON responses` to its clients (it&#39;s an `API server`, really).

Once in a while clients get 0-byte responses. It&#39;s not me returning them, however. Here is a snippet of my app&#39;s log:

&gt; Mar 14 13:13:31 d.0b1adf0a-0597-4f5c-8901-dfe7cda9bce0 app[web.1]
&gt; [2013-03-14 13:13:31 UTC] 10.104.41.136 apisrv -
&gt; api_get_credits_balance(): session_token=[MASKED]

The first line above is me starting to handle the request. 

&gt; Mar 14 13:13:31 d.0b1adf0a-0597-4f5c-8901-dfe7cda9bce0 app[web.1]
&gt; [2013-03-14 13:13:31 UTC] 10.104.41.136 apisrv 1252148511
&gt; api_get_credits_balance(): returning [{&#39;credits_balance&#39;: 0}]

The second line is me returning a value (to Flask -- it&#39;s a Flask &quot;Response&quot; object).

&gt; Mar 14 13:13:31 d.0b1adf0a-0597-4f5c-8901-dfe7cda9bce0 app[web.1]
&gt; &quot;10.104.41.136 - - [14/Mar/2013:13:13:31] &quot;POST
&gt; /get_credits_balance?session_token=MASKED HTTP/1.1&quot; 200 22 &quot;-&quot;
&gt; &quot;Appcelerator Titanium/3.0.0.GA (iPhone/6.1.2; iPhone OS; en_US;)&quot;

The third line is Gnicorn&#39;s, where you can see the Gunicorn got the 200 status and 22 bytes HTTP body (&quot;`200 22`&quot;).

However, the client got 0 bytes. Here is the Heroku router log:

&gt; Mar 14 13:13:30 d.0b1adf0a-0597-4f5c-8901-dfe7cda9bce0 heroku[router]
&gt; at=info method=POST path=/get_credits_balance?session_token=MASKED
&gt; host=matchspot-apisrv.herokuapp.com fwd=&quot;66.87.116.128&quot; dyno=web.1
&gt; queue=0 wait=0ms connect=1ms service=19ms status=200 bytes=0

Why does Gunicorn return 22 bytes, but Heroku sees 0, and indeed passes back 0 bytes to the client? Is this a Heroku bug?




Heroku truncates HTTP responses?

I&#39;ve been working on a new dev platform using nginx/gunicorn and Flask for my application.

Ops-wise, everything works fine - the issue I&#39;m having is with debugging the Flask layer. When there&#39;s an error in my code, I just get a straight 500 error returned to the browser and nothing shows up on the console or in my logs.

I&#39;ve tried many different configs/options.. I guess I **must** be missing something obvious.

My gunicorn.conf:

    import os
    
    bind = &#39;127.0.0.1:8002&#39;
    workers = 3
    backlog = 2048
    worker_class = &quot;sync&quot;
    debug = True
    proc_name = &#39;gunicorn.proc&#39;
    pidfile = &#39;/tmp/gunicorn.pid&#39;
    logfile = &#39;/var/log/gunicorn/debug.log&#39;
    loglevel = &#39;debug&#39;

An example of some Flask code that borks- testserver.py:

    from flask import Flask
    from flask import render_template_string
    from werkzeug.contrib.fixers import ProxyFix
    
    app = Flask(__name__)
    
    @app.route(&#39;/&#39;)
    def index():
        n = 1/0
        return &quot;DIV/0 worked!&quot;

And finally, the command to run the flask app in gunicorn:

    gunicorn -c gunicorn.conf.py testserver:app

Thanks y&#39;all

Debugging a Flask app running in Gunicorn

I successfully install gunicorn:

    remote: -----&gt; Removing .DS_Store files
    remote: -----&gt; Python app detected
    remote: -----&gt; Installing dependencies with pip
    remote:        Collecting gunicorn==19.0.0 (from -r requirements.txt (line 1))
    remote:          Downloading gunicorn-19.0.0.tar.gz (382kB)
    remote:        Installing collected packages: gunicorn
    remote:          Running setup.py install for gunicorn
    remote:        Successfully installed gunicorn-19.0.0

My Procfile:

    web: gunicorn myapp:app --log-file=-
 
But the app crashes when deployed:

    bash: gunicorn: command not found 

I tried adding the heroku python buildpack, but no luck. If I roll back to a previous commit (where `requirements.txt` and `Procile` are both unchanged), it works:

    heroku/web.1:  Starting process with command `gunicorn myapp:app --log-file=-` 
    app/web.1:  2015-10-08 17:04:18 [3] [INFO] Listening at: http://0.0.0.0:51854 (3)

Heroku + gunicorn not working (bash: gunicorn: command not found )

I dont know much about python. I want to start working on the project and the setup instruction says:

    pip install -r requirements-dev.txt

Simple enougth. The problem is that I get this: 

        Downloading/unpacking gunicorn==0.13.4 (from -r requirements.txt (line 7))
      Running setup.py egg_info for package gunicorn
        Traceback (most recent call last):
          File &quot;&lt;string&gt;&quot;, line 16, in &lt;module&gt;
          File &quot;/tmp/pip-build-root/gunicorn/setup.py&quot;, line 18, in &lt;module&gt;
            long_description = file(
        NameError: name &#39;file&#39; is not defined
        Complete output from command python setup.py egg_info:
        Traceback (most recent call last):
    
      File &quot;&lt;string&gt;&quot;, line 16, in &lt;module&gt;
    
      File &quot;/tmp/pip-build-root/gunicorn/setup.py&quot;, line 18, in &lt;module&gt;
    
        long_description = file(
    
    NameError: name &#39;file&#39; is not defined

I dont understand the problem. Maybe somebody can help out?

I run this on Arch Linux, python defaults to python 3 and the project is not python 3 but Im not sure if thats it.

Thanks.


python NameError: name &#39;file&#39; is not defined

I&#39;m starting gunicorn with the Django command `python manage.py run_gunicorn`. How can I stop gunicorn properly?

Note: I have a semi-automated server deployment with fabric. Thus using something like `ps aux | grep gunicorn` to kill the process manually by pid is not an option. 

How to stop gunicorn properly

I am working with configuring Django project with Nginx and Gunicorn.

While I am accessing my port `gunicorn mysite.wsgi:application --bind=127.0.0.1:8001` in Nginx server, I am getting the following error in my error log file;

&gt; 2014/05/30 11:59:42 [crit] 4075#0: *6 connect() to 127.0.0.1:8001 failed (13: Permission denied) while connecting to upstream, client: 127.0.0.1, server: localhost, request: &quot;GET / HTTP/1.1&quot;, upstream: `&quot;http://127.0.0.1:8001/&quot;`, host: &quot;localhost:8080&quot;

Below is the content of my `nginx.conf` file;

    server {
        listen 8080;
        server_name localhost;
        access_log  /var/log/nginx/example.log;
        error_log /var/log/nginx/example.error.log;

        location / {
            proxy_pass http://127.0.0.1:8001;
            proxy_set_header X-Forwarded-For $remote_addr;
            proxy_set_header Host $http_host;
        }
    }

In the HTML page I am getting `502 Bad Gateway`.

What mistake am I doing?

(13: Permission denied) while connecting to upstream:[nginx]

I&#39;m trying to add logging to a web application which uses Flask.

When hosted using the built-in server (i.e. `python3 server.py`), logging works. When hosted using Gunicorn, the log file is not created.

The simplest code which reproduces the problem is this one:

    #!/usr/bin/env python

    import logging
    from flask import Flask
    flaskApp = Flask(__name__)


    @flaskApp.route(&#39;/&#39;)
    def index():
        flaskApp.logger.info(&#39;Log message&#39;)
        print(&#39;Direct output&#39;)
        return &#39;Hello World\n&#39;


    if __name__ == &quot;__main__&quot;:
        logHandler = logging.FileHandler(&#39;/var/log/demo/app.log&#39;)
        logHandler.setLevel(logging.INFO)
        flaskApp.logger.addHandler(logHandler)
        flaskApp.logger.setLevel(logging.INFO)
        flaskApp.run()

The application is called using:

    gunicorn server:flaskApp -b :80 -w 4
        --access-gfile /var/log/demo/access.log
        --error-logfile /var/log/demo/error.log

When doing a request to the home page of the site, the following happens:

 1. I receive the expected HTTP 200 &quot;Hello World\n&quot; in response.

 1. There is a trace of the request in `/var/log/demo/access.log`.

 1. `/var/log/demo/error.log` stays the same (there are just the boot events).

 1. There is the &quot;Direct output&quot; line in the terminal.

 1. There is no &#39;/var/log/demo/app.log&#39;. If I create the file prior to launching the application, the file is not modified.

Note that:

 - The directory `/var/log/demo` can be accessed (read, write, execute) by everyone, so this is not the permissions issue.

 - If I add `StreamHandler` as a second handler, there is still no trace of the &quot;Log message&quot; message neither in the terminal, nor in Gunicorn log files.

 - Gunicorn is installed using `pip3 install gunicorn`, so there shouldn&#39;t be any mismatch with Python versions.

What&#39;s happening?

Why is Flask application not creating any logs when hosted by Gunicorn?

I was wondering what the correct approach to deploying a containerized Django app using gunicorn &amp; celery was. 

Specifically, each of these processes has a built-in way of scaling vertically, using `workers` for gunicorn and `concurrency` for celery. And then there is the Kubernetes approach to scaling using `replicas`

There is also this notion of setting workers equal to some function of the CPUs. Gunicorn recommends 
&gt;2-4 workers per core

However, I am confused what this translates to on K8s where CPU is a divisible shared resource - unless I use resoureceQuotas.

I want to understand what the Best Practice is. There are three options I can think of:

- Have single workers for gunicorn and a concurrency of 1 for celery, and scale them using the replicas? (horizontal scaling)
- Have gunicorn &amp; celery run in a single replica deployment with internal scaling (vertical scaling). This would mean setting fairly high values of workers &amp; concurrency respectively. 
- A mixed approach between 1 and 2, where we run gunicorn and celery with a small value for workers &amp; concurrency, (say 2), and then use K8s Deployment replicas to scale horizontally.

There are some questions on SO around this, but none offer an in-depth/thoughtful answer. Would appreciate if someone can share their experience.

Note: We use the default worker_class `sync` for Gunicorn

Docker/Kubernetes + Gunicorn/Celery - Multiple Workers vs Replicas?

Im looking for something better than ``sudo restart projectname`` every time I issue a ``git pull origin master``, which pulls down my latest changes to a Django project. This ``restart`` command, I believe, is related to Upstart, which I use to start/top my Gunicorn server process.

This restart causes a brief outage. Users hitting the web server (nginx) will get a 500, because Gunicorn is still restarting. In fact, it seems to restart instantly, but it takes a few seconds for pages to load.

Any ideas on how to make this seamless? Ideally, I&#39;d like to issue my ``git pull`` and Gunicorn reloads automatically.

A better way to restart/reload Gunicorn (via Upstart) after &#39;git pull&#39;ing my Django projects

I see people are running setups like Nginx + Gunicorn + Flask.

Can someone explain what is the benefit of having Gunicorn in front of Flask? Why not just run Flask alone? Doesn&#39;t it consume more resources having Gunicorn + Flask running? Is Gunicorn able to reboot the Flask instance when it fails to respond?

What&#39;s also the purpose of having nginx on top of gunicorn? Isn&#39;t gunicorn enough? Again, more resources being spent?

What benefit is added by using Gunicorn + Nginx + Flask?

We&#39;ve got a few Django setups that go through a proxy (Apache and Nginx) that eventually make their way to the actual Django runtime.

We need to have HTTPS end to end even once it&#39;s in our network.  We&#39;ve been revisiting Gunicorn due to its success and performance in our other setups, but needed to test with HTTPS end to end to be consistent.

Our topology is as such:

https://foo.com -&gt; [Public facing proxy] -&gt; (https) -&gt; [internal server https://192...:8001]

How does one configure Gunicorn to listen on HTTPS with a self signed certificate?  

Running gunicorn on https?

I&#39;m new to heroku and gunicorn so I&#39;m not sure how this works.  But I&#39;ve done some searching and I think I&#39;m close to deploying my Django app (1.5.1).  So I know I need a Procfile which has


    web: gunicorn app.wsgi

Because my directories are a bit different. I can&#39;t run gunicorn in the root directory

    app_project
        requirements/
        contributors/
        app/
            app/
                settings/
                wsgi.py
            # Normally Procfile goes here
        Procfile

Normally app/ would be the root directory, but I decided to structure my folders this way to separate my django app from some other things.  Since I have to put the Procfile in the root directory for heroku to recognize it, what should I put in the Procfile and/or what parameters should I place in the gunicorn command?


Note:

    web: gunicorn app.wsgi # won&#39;t work because Procfile is in a directory above
                           # I also want to keep the directories as is
                           # I also don&#39;t want to create a secondary git inside the app folder just for heroku
    web: gunicorn app.app.wsgi # won&#39;t work because I don&#39;t want to convert the folder into a python module




How can I modify Procfile to run Gunicorn process in a non-standard folder on Heroku?

I wrote a flask app using the application factory pattern.  That means it doesn&#39;t create an app instance automatically when you import it.  You have to call create_app for that.  Now how do I run it in gunicorn?

How do I run a flask app in gunicorn if I used the application factory pattern?

I&#39;m running django on gunicorn+nginx. I&#39;m facing a problem with file uploads. Actually uploads are working fine but gunicorn times out thus causing this in nginx:

    2011/07/25 12:13:47 [error] 15169#0: *2317 upstream timed out (110: Connection timed out) while reading response header from upstream, client: IP-ADDRESS, server: SERVER, request: &quot;GET /photos/events/event/25 HTTP/1.1&quot;, upstream: &quot;http://127.0.0.1:29000/photos/events/event/25&quot;, host: &quot;HOST&quot;, referrer: &quot;REFERER_ADDRESS&quot;

If I refresh the page, I can see all the photos are uploaded just fine. The problem is that it causes a timeout thus giving the impression that upload did not work.

here is my gunicorn conf:

    bind = &quot;127.0.0.1:29000&quot;
    logfile = &quot;/path/to/logs/gunicorn.log&quot;
    workers = 3

I tried changing timeout but it didn&#39;t work.


110: Connection timed out (Nginx/Gunicorn)

I want to make a Flask+Nginx+Gunicorn deployment. I have Nginx setup and running and I run gunicorn as described in the docs:

    gunicorn app:app

But when I logout of the server the gunicorn process exits? What is the correct way to make sure it stay running for Nginx to connect to, and restarts if it crashes?

All Gunicorn Solutions on Gang of Coders

Total of 30 Gunicorn Solutions