will be shown on the console by default. See Logging to change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 1:8080 Using host and port is also supported: [server:main] host = 127.0.0.1 port = 8080 The PasteDeploy syntax for UNIX domain sockets is analagous: [server:main] use = egg:waitress#main unix_socket sock You can find more settings to tweak (arguments to waitress.serve or equivalent settings in PasteDeploy) in Arguments to waitress.serve. Additionally, there is a command line runner called waitress-serve

setting. You can use it by passing script_name='/foo' to waitress.serve or you can use it in a PasteDeploy ini file as script_name = /foo. This will cause the WSGI SCRIPT_NAME value to be the value passed request which is prefixed with this value to be stripped of the prefix. You can use this instead of PasteDeploy's prefixmiddleware to always prefix the path. 0.8.5 (2013-05-27) Fix runner multisegment imports shown on the console by default. See Access Logging to change this. There's an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress's WSGI gateway from a configuration file, e.g.:

shown on the console by default. See Access Logging to change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 1:8080 Using host and port is also supported: [server:main] host = 127.0.0.1 port = 8080 The PasteDeploy syntax for UNIX domain sockets is analagous: [server:main] use = egg:waitress#main unix_socket sock You can find more settings to tweak (arguments to waitress.serve or equivalent settings in PasteDeploy) in Arguments to waitress.serve. Additionally, there is a command line runner called waitress-serve

setting. You can use it by passing script_name='/foo' to waitress.serve or you can use it in a PasteDeploy ini file as script_name = /foo. This will cause the WSGI SCRIPT_NAME value to be the value passed request which is prefixed with this value to be stripped of the prefix. You can use this instead of PasteDeploy's prefixmiddleware to always prefix the path. 0.8.5 (2013-05-27) Fix runner multisegment imports shown on the console by default. See Access Logging to change this. There's an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress's WSGI gateway from a configuration file, e.g.:

setting. You can use it by passing script_name='/foo' to waitress.serve or you can use it in a PasteDeploy ini file as script_name = /foo. This will cause the WSGI SCRIPT_NAME value to be the value passed request which is prefixed with this value to be stripped of the prefix. You can use this instead of PasteDeploy's prefixmiddleware to always prefix the path. 0.8.5 (2013-05-27) Fix runner multisegment imports shown on the console by default. See Access Logging to change this. There's an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress's WSGI gateway from a configuration file, e.g.:

shown on the console by default. See Access Logging to change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 1:8080 Using host and port is also supported: [server:main] host = 127.0.0.1 port = 8080 The PasteDeploy syntax for UNIX domain sockets is analagous: [server:main] use = egg:waitress#main unix_socket sock You can find more settings to tweak (arguments to waitress.serve or equivalent settings in PasteDeploy) in Arguments to waitress.serve. Additionally, there is a command line runner called waitress-serve

setting. You can use it by passing script_name='/foo' to waitress.serve or you can use it in a PasteDeploy ini file as script_name = /foo. This will cause the WSGI SCRIPT_NAME value to be the value passed request which is prefixed with this value to be stripped of the prefix. You can use this instead of PasteDeploy's prefixmiddleware to always prefix the path. 0.8.5 (2013-05-27) Fix runner multisegment imports shown on the console by default. See Access Logging to change this. There's an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress's WSGI gateway from a configuration file, e.g.:

shown on the console by default. See Access Logging to change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 1:8080 Using host and port is also supported: [server:main] host = 127.0.0.1 port = 8080 The PasteDeploy syntax for UNIX domain sockets is analagous: [server:main] use = egg:waitress#main unix_socket sock You can find more settings to tweak (arguments to waitress.serve or equivalent settings in PasteDeploy) in Arguments to waitress.serve. Additionally, there is a command line runner called waitress-serve

shown on the console by default. See Access Logging to change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 1:8080 Using host and port is also supported: [server:main] host = 127.0.0.1 port = 8080 The PasteDeploy syntax for UNIX domain sockets is analagous: [server:main] use = egg:waitress#main unix_socket sock You can find more settings to tweak (arguments to waitress.serve or equivalent settings in PasteDeploy) in Arguments to waitress.serve. Additionally, there is a command line runner called waitress-serve

shown on the console by default. See Access Logging to change this. There's an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress's WSGI gateway from a configuration file, e.g.: supported: [server:main] host = 127.0.0.1 port = 8080 3 waitress Documentation, Release 3.0.1 The PasteDeploy syntax for UNIX domain sockets is analogous: [server:main] use = egg:waitress#main unix_socket sock You can find more settings to tweak (arguments to waitress.serve or equivalent settings in PasteDeploy) in Argu- ments to waitress.serve. Additionally, there is a command line runner called waitress-serve