809
by Canonical.com Patch Queue Manager
Nuke some arch-tags |
1 |
# identify the component configuration used to define the site: |
2 |
site-definition site.zcml |
|
3 |
||
4 |
# number of bytecode instructions to execute between checks for |
|
5 |
# interruptions (SIGINTR, thread switches): |
|
6 |
interrupt-check-interval 200 |
|
7 |
||
8 |
<server>
|
|
9 |
type HTTP |
|
10 |
address 8085 |
|
11 |
</server>
|
|
12 |
||
13 |
# For debugging purposes, you can use this publisher instead/as well |
|
14 |
# (obviously if it's as well, use a different port number). If there's |
|
15 |
# an exception, Zope will drop into pdb at the point of the exception. |
|
16 |
<server>
|
|
17 |
type PostmortemDebuggingHTTP |
|
18 |
address 8089 |
|
19 |
</server>
|
|
20 |
||
21 |
<server>
|
|
22 |
type DebugLayerHTTP |
|
23 |
address 8086 |
|
24 |
</server>
|
|
25 |
||
26 |
##<server>
|
|
27 |
## type FTP |
|
28 |
## address 8021 |
|
29 |
##</server>
|
|
30 |
||
31 |
# non-persistent in-memory storage |
|
32 |
<zodb>
|
|
33 |
<mappingstorage/>
|
|
34 |
</zodb>
|
|
35 |
||
36 |
<accesslog>
|
|
37 |
# This sets up logging to both a file (access.log) and to standard |
|
38 |
# output (STDOUT). The "path" setting can be a relative or absolute |
|
39 |
# filesystem path or the tokens STDOUT or STDERR. |
|
40 |
||
41 |
<logfile>
|
|
42 |
path launchpad-access.log |
|
43 |
</logfile>
|
|
44 |
||
45 |
<logfile>
|
|
46 |
path STDOUT |
|
47 |
</logfile>
|
|
48 |
</accesslog>
|
|
49 |
||
50 |
<eventlog>
|
|
51 |
# This sets up logging to both a file (z3.log) and to standard |
|
52 |
# output (STDOUT). The "path" setting can be a relative or absolute |
|
53 |
# filesystem path or the tokens STDOUT or STDERR. |
|
54 |
||
55 |
<logfile>
|
|
56 |
path launchpad.log |
|
57 |
</logfile>
|
|
58 |
||
59 |
<logfile>
|
|
60 |
path STDOUT |
|
61 |
</logfile>
|
|
62 |
</eventlog>
|
|
63 |