 |
 |
 |
Aspen |  |
|
|
|
|
|
Aspen | |
|
|
This section describes the general Aspen configuration file at
__/etc/aspen.conf. Additional configuration files are described in the
"Extending Aspen" chapter. aspen.conf is in .ini-style format per
the ConfigParser module. Aspen responds to the following settings in
the main section. You may define additional settings and sections that
are meaningful to your application, which you may access using the
aspen.conf object described below in the "API" chapter.
| Option | Description | Default |
|---|---|---|
| address | The address to which Aspen should bind. If address
begins with a dot or a forward slash, then it is interpreted as an AF_UNIX
socket. If it contains more than one colon, it is seen as an AF_INET6 address.
Otherwise, it is interpreted as AF_INET. If address begins with a colon,
the IP address defaults to 0.0.0.0. |
0.0.0.0:8080 |
| defaults | A comma-separated list of names to look for when a directory is requested. Any default resource is located immediately before dispatching to a handler. | index.html, index.htm |
| http_version | The version of HTTP to speak, either 1.0 or
1.1. |
1.1 |
| mode | One of debugging, development, staging, or
production. In debugging and development modes, Aspen will restart itself
any time configuration files or module source files change on the
filesystem. |
development |
| threads | The number of threads to maintain in the request-servicing thread pool. | 10 |
Here is an example aspen.conf configuration file:
[main] address = :8000 [myapp] knob = true
See Also:
mode
|
|
|
Aspen | |
|
|