36 lines
1.3 KiB
Plaintext
36 lines
1.3 KiB
Plaintext
|
## Path: Network/WWW/uWSGI
|
||
|
## Description: Run uWSGI in Emperor Mode
|
||
|
## Type: boolean
|
||
|
## Default: true
|
||
|
#
|
||
|
# uWSGI emperor mode is a method of running many different applications
|
||
|
# (vassals) in individual uWSGI processes, managed by a single master (emperor)
|
||
|
# process. It is recommended in most cases.
|
||
|
#
|
||
|
UWSGI_EMPEROR_MODE=true
|
||
|
|
||
|
## Path: Network/WWW/uWSGI
|
||
|
## Description: uWSGI Vassals Directory
|
||
|
## Type: string
|
||
|
## Default: /etc/uwsgi/vassals
|
||
|
#
|
||
|
# When uWSGI is running in emperor mode, this is the directory where individual
|
||
|
# application configurations (vassals) are found. Configuration files can be in
|
||
|
# xml, ini, yaml, and json format. Vassals are started automatically when a
|
||
|
# file is placed in this directory and restarted if a file is changed.
|
||
|
#
|
||
|
UWSGI_VASSALS="/etc/uwsgi/vassals/"
|
||
|
|
||
|
## Path: Network/WWW/uWSGI
|
||
|
## Description: Additional uWSGI Options
|
||
|
## Type: string
|
||
|
## Default: ""
|
||
|
#
|
||
|
# Specify additional uWSGI options here. This is normally unnecessary since
|
||
|
# options can be specified in per-application configuration files when running
|
||
|
# in emperor mode. However, if emperor mode is disabled, this option will be
|
||
|
# necessary. If emperor mode is enabled, these options are specified in
|
||
|
# addition to the emperor mode settings.
|
||
|
#
|
||
|
UWSGI_OPTIONS=""
|