GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

GUNICORN - WSGI SERVER Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy. SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched CONFIGURATION OVERVIEW In your INI file, you can specify to use Gunicorn as the server like such: use = egg:gunicorn#main host = 192.168.0.1 port = 80 workers = 2 proc_name = brim. Any parameters that Gunicorn knows about will automatically be inserted into the base configuration. Remember that these will be overridden by the config file and/or the DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

GUNICORN - WSGI SERVER Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy. SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched CONFIGURATION OVERVIEW In your INI file, you can specify to use Gunicorn as the server like such: use = egg:gunicorn#main host = 192.168.0.1 port = 80 workers = 2 proc_name = brim. Any parameters that Gunicorn knows about will automatically be inserted into the base configuration. Remember that these will be overridden by the config file and/or the DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CHANGELOG - 2021

20.1.0 - 2021-02-12 ¶. document WEB_CONCURRENCY is set by, at least, Heroku. capture peername from accept: Avoid calls to getpeername by capturing the peer name returned by accept. log a warning when a worker was terminated due to a signal. fix tornado usage with latest versions of Django. fix systemd socket activation example.

INSTALLATION

Note. There is a limited support version of Gunicorn that is compatible with Python 2.4. This fork is managed by Randall Leeds and can be found here on github.To install this version you must specify the full url to something like pip.This hasn’t been tested wtih easy_install just yet: COMMUNITY — GUNICORN 20.1.0 DOCUMENTATION Gunicorn uses GitHub for the project management. GitHub issues are used for 3 different purposes: Bug tracker : to check latest bug. Forum : Stackoverflow-style questions about Gunicorn usage. Mailing list : Discussion of Gunicorn development, new features and project management. Project maintenance guidelines are avaible on the wiki .

INSTRUMENTATION

Instrumentation. New in version 19.1. Gunicorn provides an optional instrumentation of the arbiter and workers using the statsD protocol over UDP. Thanks to the gunicorn.instrument.statsd module, Gunicorn becomes a statsD client. The use of UDP cleanly isolates Gunicorn from the receiving end of the statsD metrics so that instrumentation does FAQ — GUNICORN 20.1.0 DOCUMENTATION If you install the Python package setproctitle Gunicorn will set the process names to something a bit more meaningful. This will affect the output you see in tools like ps and top. This helps for distinguishing the master process as well as between masters when running more than one app on a single machine. See the proc_name setting for more CHANGELOG — GUNICORN 20.1.0 DOCUMENTATION Document how to serve WSGI app modules from Gunicorn. Provide guidance on X-Forwarded-For access log in documentation. Add support for named constants in the –ssl-version flag. Clarify log format usage of header & environment in documentation. Fixed systemd documentation to properly setup gunicorn GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy. DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

INSTALLATION

Note. There is a limited support version of Gunicorn that is compatible with Python 2.4. This fork is managed by Randall Leeds and can be found here on github.To install this version you must specify the full url to something like pip.This hasn’t been tested wtih easy_install just yet:

INSTRUMENTATION

Instrumentation. New in version 19.1. Gunicorn provides an optional instrumentation of the arbiter and workers using the statsD protocol over UDP. Thanks to the gunicorn.instrument.statsd module, Gunicorn becomes a statsD client. The use of UDP cleanly isolates Gunicorn from the receiving end of the statsD metrics so that instrumentation does

CUSTOM APPLICATION

gunicorn.app.wsgiapp exampleapi:app. This command will work with any Gunicorn CLI parameters or a config file - just pass them along as if you’re directly giving them to Gunicorn: # Custom parameters $ python gunicorn.app.wsgiapp exampleapi:app --bind =0 .0.0.0:8081 --workers =4 # Using a config file $ python gunicorn.app.wsgiapp

exampleapi

CHANGELOG — GUNICORN 20.1.0 DOCUMENTATION Document how to serve WSGI app modules from Gunicorn. Provide guidance on X-Forwarded-For access log in documentation. Add support for named constants in the –ssl-version flag. Clarify log format usage of header & environment in documentation. Fixed systemd documentation to properly setup gunicorn FAQ — GUNICORN 20.1.0 DOCUMENTATION If you install the Python package setproctitle Gunicorn will set the process names to something a bit more meaningful. This will affect the output you see in tools like ps and top. This helps for distinguishing the master process as well as between masters when running more than one app on a single machine. See the proc_name setting for more GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

SIGNALS HANDLING

First, replace old binary with a new one, then send USR2 signal to the master process. It renames its .pid file to .oldbin (e.g. /var/run/gunicorn.pid.oldbin), then executes a new binary, which in turn starts a new master process and the new worker processes: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 20844 benoitc 20 0

54808 11m

GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy. DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

INSTALLATION

Note. There is a limited support version of Gunicorn that is compatible with Python 2.4. This fork is managed by Randall Leeds and can be found here on github.To install this version you must specify the full url to something like pip.This hasn’t been tested wtih easy_install just yet:

INSTRUMENTATION

Instrumentation. New in version 19.1. Gunicorn provides an optional instrumentation of the arbiter and workers using the statsD protocol over UDP. Thanks to the gunicorn.instrument.statsd module, Gunicorn becomes a statsD client. The use of UDP cleanly isolates Gunicorn from the receiving end of the statsD metrics so that instrumentation does

CUSTOM APPLICATION

gunicorn.app.wsgiapp exampleapi:app. This command will work with any Gunicorn CLI parameters or a config file - just pass them along as if you’re directly giving them to Gunicorn: # Custom parameters $ python gunicorn.app.wsgiapp exampleapi:app --bind =0 .0.0.0:8081 --workers =4 # Using a config file $ python gunicorn.app.wsgiapp

exampleapi

CHANGELOG — GUNICORN 20.1.0 DOCUMENTATION Document how to serve WSGI app modules from Gunicorn. Provide guidance on X-Forwarded-For access log in documentation. Add support for named constants in the –ssl-version flag. Clarify log format usage of header & environment in documentation. Fixed systemd documentation to properly setup gunicorn FAQ — GUNICORN 20.1.0 DOCUMENTATION If you install the Python package setproctitle Gunicorn will set the process names to something a bit more meaningful. This will affect the output you see in tools like ps and top. This helps for distinguishing the master process as well as between masters when running more than one app on a single machine. See the proc_name setting for more GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

SIGNALS HANDLING

First, replace old binary with a new one, then send USR2 signal to the master process. It renames its .pid file to .oldbin (e.g. /var/run/gunicorn.pid.oldbin), then executes a new binary, which in turn starts a new master process and the new worker processes: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 20844 benoitc 20 0

54808 11m

GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy. SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line. CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

CHANGELOG - 2020

Add –print-config option to print the resolved settings at startup. remove the –log-dict-config CLI flag because it never had a working format (the logconfig_dict setting in configuration files continues to work) minimum version is Python 3.5. miscellaneous changes in

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy. SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line. CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

CHANGELOG - 2020

Add –print-config option to print the resolved settings at startup. remove the –log-dict-config CLI flag because it never had a working format (the logconfig_dict setting in configuration files continues to work) minimum version is Python 3.5. miscellaneous changes in

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. COMMUNITY — GUNICORN 20.1.0 DOCUMENTATION Gunicorn uses GitHub for the project management. GitHub issues are used for 3 different purposes: Bug tracker : to check latest bug. Forum : Stackoverflow-style questions about Gunicorn usage. Mailing list : Discussion of Gunicorn development, new features and project management. Project maintenance guidelines are avaible on the wiki . GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

INSTRUMENTATION

Instrumentation. New in version 19.1. Gunicorn provides an optional instrumentation of the arbiter and workers using the statsD protocol over UDP. Thanks to the gunicorn.instrument.statsd module, Gunicorn becomes a statsD client. The use of UDP cleanly isolates Gunicorn from the receiving end of the statsD metrics so that instrumentation does

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. CONFIGURATION OVERVIEW Configuration Overview. ¶. Gunicorn pulls configuration information from three distinct places. The first place that Gunicorn will read configuration from is the framework specific configuration file. Currently this only affects Paster applications. The second source of configuration information is a configuration file that is optionally

CHANGELOG - 2021

20.1.0 - 2021-02-12 ¶. document WEB_CONCURRENCY is set by, at least, Heroku. capture peername from accept: Avoid calls to getpeername by capturing the peer name returned by accept. log a warning when a worker was terminated due to a signal. fix tornado usage with latest versions of Django. fix systemd socket activation example.

RUNNING GUNICORN

paster serve ¶. If you’re wanting to keep on keeping on with the usual paster serve command, you can specify the Gunicorn server settings in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 5000. And then as per usual:

$ cd

FAQ — GUNICORN 20.1.0 DOCUMENTATION If you install the Python package setproctitle Gunicorn will set the process names to something a bit more meaningful. This will affect the output you see in tools like ps and top. This helps for distinguishing the master process as well as between masters when running more than one app on a single machine. See the proc_name setting for more

CUSTOM APPLICATION

This command will work with any Gunicorn CLI parameters or a config file - just pass them along as if you’re directly giving them to Gunicorn: # Custom parameters $ python gunicorn.app.wsgiapp exampleapi:app --bind =0 .0.0.0:8081 --workers =4 # Using a config file $ python gunicorn.app.wsgiapp exampleapi:app -c config.py. CHANGELOG — GUNICORN 20.1.0 DOCUMENTATION Document how to serve WSGI app modules from Gunicorn. Provide guidance on X-Forwarded-For access log in documentation. Add support for named constants in the –ssl-version flag. Clarify log format usage of header & environment in documentation. Fixed systemd documentation to properly setup gunicorn GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

CHANGELOG - 2020

Add –print-config option to print the resolved settings at startup. remove the –log-dict-config CLI flag because it never had a working format (the logconfig_dict setting in configuration files continues to work) minimum version is Python 3.5. miscellaneous changes in

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

CHANGELOG - 2020

Add –print-config option to print the resolved settings at startup. remove the –log-dict-config CLI flag because it never had a working format (the logconfig_dict setting in configuration files continues to work) minimum version is Python 3.5. miscellaneous changes in

SIGNAL HANDLING

The HUP signal can be used to reload the Gunicorn configuration on the fly. Sending a HUP signal will reload the configuration, start the new worker processes with a new configuration and gracefully shutdown older workers. If the application is not preloaded (using the preload_app option), Gunicorn will also load the new version of it. GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

GUNICORN - WSGI SERVER Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

COMMUNITY — GUNICORN 20.1.0 DOCUMENTATION Gunicorn uses GitHub for the project management. GitHub issues are used for 3 different purposes: Bug tracker : to check latest bug. Forum : Stackoverflow-style questions about Gunicorn usage. Mailing list : Discussion of Gunicorn development, new features and project management. Project maintenance guidelines are avaible on the wiki .

INSTALLATION

Note. There is a limited support version of Gunicorn that is compatible with Python 2.4. This fork is managed by Randall Leeds and can be found here on github.To install this version you must specify the full url to something like pip.This hasn’t been tested wtih easy_install just yet:

INSTRUMENTATION

Instrumentation. New in version 19.1. Gunicorn provides an optional instrumentation of the arbiter and workers using the statsD protocol over UDP. Thanks to the gunicorn.instrument.statsd module, Gunicorn becomes a statsD client. The use of UDP cleanly isolates Gunicorn from the receiving end of the statsD metrics so that instrumentation does

CHANGELOG - 2021

20.1.0 - 2021-02-12 ¶. document WEB_CONCURRENCY is set by, at least, Heroku. capture peername from accept: Avoid calls to getpeername by capturing the peer name returned by accept. log a warning when a worker was terminated due to a signal. fix tornado usage with latest versions of Django. fix systemd socket activation example. CHANGELOG — GUNICORN 20.1.0 DOCUMENTATION Document how to serve WSGI app modules from Gunicorn. Provide guidance on X-Forwarded-For access log in documentation. Add support for named constants in the –ssl-version flag. Clarify log format usage of header & environment in documentation. Fixed systemd documentation to properly setup gunicorn GUNICORN DOCUMENTATION CHAPTER 1 Features •Natively supports WSGI, Django, and Paster •Automatic worker process management •Simple Python configuration •Multiple worker configurations GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

COMMUNITY — GUNICORN 20.1.0 DOCUMENTATION Gunicorn uses GitHub for the project management. GitHub issues are used for 3 different purposes: Bug tracker : to check latest bug. Forum : Stackoverflow-style questions about Gunicorn usage. Mailing list : Discussion of Gunicorn development, new features and project management. Project maintenance guidelines are avaible on the wiki . DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH). GUNICORN - PYTHON WSGI HTTP SERVER FOR UNIXINSTALLATIONDEPLOYING GUNICORNCONFIGURATION OVERVIEWDESIGNSTABLERUNNING GUNICORN Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx . Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Gunicorn uses GitHub for the project management. GitHub issues are used for 3

RUNNING GUNICORN

To use Gunicorn with these commands, specify it as a server in your configuration file: use = egg:gunicorn#main host = 127.0.0.1 port = 8080 workers = 3. This approach is the quickest way to get started with Gunicorn, but there are some limitations. Gunicorn will have no control over how the application is loaded, so settings

such

INSTALLATION

Debian GNU/Linux¶. If you are using Debian GNU/Linux it is recommended that you use system packages to install Gunicorn except maybe when you want to use different versions of Gunicorn with

virtualenv.

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched SETTINGS — GUNICORN 20.1.0 DOCUMENTATION Settings ¶. Settings. This is an exhaustive list of settings for Gunicorn. Some settings are only able to be set from a configuration file. The setting name is what should be used in the configuration file. The command line arguments are listed as well for reference on setting at the command line.

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can any other applications that should be launched at the same time. Then you can start your gunicorn application using gafferp .: gafferp start. If gafferd is launched you

can

COMMUNITY — GUNICORN 20.1.0 DOCUMENTATION Gunicorn uses GitHub for the project management. GitHub issues are used for 3 different purposes: Bug tracker : to check latest bug. Forum : Stackoverflow-style questions about Gunicorn usage. Mailing list : Discussion of Gunicorn development, new features and project management. Project maintenance guidelines are avaible on the wiki . DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

CONFIGURATION OVERVIEW Configuration File¶. The configuration file should be a valid Python source file with a python extension (e.g. gunicorn.conf.py).It only needs to be readable from the file system. More specifically, it does not have to be on the module path (sys.path, PYTHONPATH).

DEPLOYING GUNICORN

Using a Procfile ¶. Create a Procfile in your project: gunicorn = gunicorn -w 3 test:app. You can launch any other applications that should be launched at the same time. Then you can start your Gunicorn application using Gaffer: gaffer start. If gafferd is launched DESIGN — GUNICORN 20.1.0 DOCUMENTATION Master ¶. The master process is a simple loop that listens for various process signals and reacts accordingly. It manages the list of running workers by listening for signals like TTIN, TTOU, and CHLD. TTIN and TTOU tell the master to increase or decrease the number of running workers. CHLD indicates that a child process has terminated,

in

GUNICORN - WSGI SERVER Gunicorn - WSGI server. Gunicorn ‘Green Unicorn’ is a Python WSGI HTTP Server for UNIX. It’s a pre-fork worker model ported from Ruby’s Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

CHANGELOG - 2020

Add –print-config option to print the resolved settings at startup. remove the –log-dict-config CLI flag because it never had a working format (the logconfig_dict setting in configuration files continues to work) minimum version is Python 3.5. miscellaneous changes in

INSTALLATION

Note. There is a limited support version of Gunicorn that is compatible with Python 2.4. This fork is managed by Randall Leeds and can be found here on github.To install this version you must specify the full url to something like pip.This hasn’t been tested wtih easy_install just yet:

INSTRUMENTATION

Instrumentation. New in version 19.1. Gunicorn provides an optional instrumentation of the arbiter and workers using the statsD protocol over UDP. Thanks to the gunicorn.instrument.statsd module, Gunicorn becomes a statsD client. The use of UDP cleanly isolates Gunicorn from the receiving end of the statsD metrics so that instrumentation does

CUSTOM APPLICATION

This command will work with any Gunicorn CLI parameters or a config file - just pass them along as if you’re directly giving them to Gunicorn: # Custom parameters $ python gunicorn.app.wsgiapp exampleapi:app --bind =0 .0.0.0:8081 --workers =4 # Using a config file $ python gunicorn.app.wsgiapp exampleapi:app -c config.py. CHANGELOG — GUNICORN 20.1.0 DOCUMENTATION Document how to serve WSGI app modules from Gunicorn. Provide guidance on X-Forwarded-For access log in documentation. Add support for named constants in the –ssl-version flag. Clarify log format usage of header & environment in documentation. Fixed systemd documentation to properly setup gunicorn CONFIGURATION OVERVIEW Configuration Overview. ¶. Gunicorn pulls configuration information from three distinct places. The first place that Gunicorn will read configuration from is the framework specific configuration file. Currently this only affects Paster applications. The second source of configuration information is a configuration file that is optionally FAQ — GUNICORN 20.1.0 DOCUMENTATION If you install the Python package setproctitle Gunicorn will set the process names to something a bit more meaningful. This will affect the output you see in tools like ps and top. This helps for distinguishing the master process as well as between masters when running more than one app on a single machine. See the proc_name setting for more Latest version: 20.1.0 GUNICORN 'GREEN UNICORN' IS A PYTHON WSGI HTTP SERVER FOR UNIX. IT'S A PRE-FORK WORKER MODEL. THE GUNICORN SERVER IS BROADLY COMPATIBLE WITH VARIOUS WEB FRAMEWORKS, SIMPLY IMPLEMENTED, LIGHT ON SERVER RESOURCES,

AND FAIRLY SPEEDY.

View source Download

*

QUICKSTART

Read the quickstart guide to get started using Gunicorn.

*

DEPLOYMENT

Learn how to deploy the Gunicorn server.

*

COMMUNITY

Get in touch with the community.

*

DOCUMENTATION

Read the documentation to learn more about Gunicorn.

INSTALLATION

Here's a quick rundown on how to get started with Gunicorn. For more details read the documentation . $ pip install gunicorn

$ cat myapp.py

def app(environ, start_response): data = b"Hello, World!\n" start_response("200 OK", )

return iter()

$ gunicorn -w 4 myapp:app Listening at: http://127.0.0.1:8000 (30869) Using worker: sync Booting worker with pid: 30874 Booting worker with pid: 30875 Booting worker with pid: 30876 Booting worker with pid: 30877

DEPLOYMENT

Gunicorn is a WSGI HTTP server. It is best to use Gunicorn behind an HTTP proxy server. We strongly advise you to use nginx

.

Here's an example to help you get started with using nginx:

server {

listen 80;

server_name example.org; access_log  /var/log/nginx/example.log;

location / {

proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

}

}

Nginx is set up as reverse proxy server to a Gunicorn server running on localhost port 8000. Read the full documentation at docs.gunicorn.org

PROJECT MANAGEMENT

GUNICORN uses GitHub for the project management . GitHub issues are used for 3 different purposes:

* Bug tracker

* Forum

* Mailing list

Project maintenance guidelines are avaible on the wiki

IRC

The Gunicorn channel is on the Freenode IRC network. You can chat with the community on the #gunicorn channel

.

ISSUE TRACKING

Bug reports, enhancement requests and tasks generally go in the Github

issue tracker .

SECURITY ISSUES

The security mailing list is a place to report security issues. Only developers are subscribed to it. To post a message to the list use the address security@gunicorn.org

DOCUMENTATION

You can read more comprehensive documentation at docs.gunicorn.org

.

The contents are:

* Installation

* Running Gunicorn

* Configuration Overview * Deploying Gunicorn

* Design

* FAQ

* Changelog

This open sourced site is hosted on GitHub. Patches, suggestions, and comments are welcome.