vigigraph / development.ini @ b8b576c5
History | View | Annotate | Download (4.61 KB)
1 |
# |
---|---|
2 |
# vigigraph - Pylons development environment configuration |
3 |
# |
4 |
# The %(here)s variable will be replaced with the parent directory of this file |
5 |
# |
6 |
# This file is for deployment specific config options -- other configuration |
7 |
# that is always required for the app is done in the config directory, |
8 |
# and generally should not be modified by end users. |
9 |
|
10 |
[DEFAULT] |
11 |
debug = true |
12 |
# Uncomment and replace with the address which should receive any error reports |
13 |
#email_to = you@yourdomain.com |
14 |
smtp_server = localhost |
15 |
error_email_from = paste@localhost |
16 |
|
17 |
[server:main] |
18 |
use = egg:Paste#http |
19 |
host = 0.0.0.0 |
20 |
port = 8082 |
21 |
|
22 |
[app:main] |
23 |
use = egg:vigigraph |
24 |
|
25 |
db_basename=vigilo_ |
26 |
;password_hashing_function=md5 |
27 |
lang=fr |
28 |
use_kerberos=False |
29 |
app.vigicore = / |
30 |
|
31 |
# URL |
32 |
rrd_url = http://localhost/rrdgraph |
33 |
nagios_url = http://localhost/nagios/cgi-bin |
34 |
|
35 |
# Vigigraph - refresh for graphs (en millisecondes) |
36 |
delay_refresh = 30000 |
37 |
|
38 |
# separateurs pour export CSV |
39 |
# - entre valeurs consecutives |
40 |
export_csv_sep_values = ; |
41 |
# - dans une valeur |
42 |
export_csv_sep_value = , |
43 |
|
44 |
full_stack = true |
45 |
cache_dir = %(here)s/data |
46 |
beaker.session.key = vigigraph |
47 |
beaker.session.secret = vigilo |
48 |
sa_auth.cookie_secret = vigilo |
49 |
|
50 |
# If you'd like to fine-tune the individual locations of the cache data dirs |
51 |
# for the Cache data, or the Session saves, un-comment the desired settings |
52 |
# here: |
53 |
#beaker.cache.data_dir = %(here)s/data/cache |
54 |
#beaker.session.data_dir = %(here)s/data/sessions |
55 |
|
56 |
# pick the form for your database |
57 |
# %(here) may include a ':' character on Windows environments; this can |
58 |
# invalidate the URI when specifying a SQLite db via path name |
59 |
# sqlalchemy.url=postgres://username:password@hostname:port/databasename |
60 |
# sqlalchemy.url=mysql://username:password@hostname:port/databasename |
61 |
|
62 |
|
63 |
# If you have sqlite, here's a simple default to get you started |
64 |
# in development |
65 |
|
66 |
sqlalchemy.url=postgres://vigilo:vigilo@localhost/vigilo |
67 |
#sqlalchemy.url = sqlite:///%(here)s/devdata.db |
68 |
#echo shouldn't be used together with the logging module. |
69 |
sqlalchemy.echo = false |
70 |
sqlalchemy.echo_pool = false |
71 |
sqlalchemy.pool_recycle = 3600 |
72 |
|
73 |
# if you are using Mako and want to be able to reload |
74 |
# the mako template from disk during the development phase |
75 |
# you should say 'true' here |
76 |
# This option is only used for mako templating engine |
77 |
# WARNING: if you want to deploy your application using a zipped egg |
78 |
# (ie: if your application's setup.py defines zip-safe=True, then you |
79 |
# MUST put "false" for the production environment because there will |
80 |
# be no disk and real files to compare time with. |
81 |
# On the contrary if your application defines zip-safe=False and is |
82 |
# deployed in an unzipped manner, then you can leave this option to true |
83 |
templating.mako.reloadfromdisk = true |
84 |
|
85 |
# the compiled template dir is a directory that must be readable by your |
86 |
# webserver. It will be used to store the resulting templates once compiled |
87 |
# by the TemplateLookup system. |
88 |
# During development you generally don't need this option since paste's HTTP |
89 |
# server will have access to you development directories, but in production |
90 |
# you'll most certainly want to have apache or nginx to write in a directory |
91 |
# that does not contain any source code in any form for obvious security reasons. |
92 |
# |
93 |
#templating.mako.compiled_templates_dir = /some/dir/where/webserver/has/access |
94 |
|
95 |
# WARNING: *THE LINE BELOW MUST BE UNCOMMENTED ON A PRODUCTION ENVIRONMENT* |
96 |
# Debug mode will enable the interactive debugging tool, allowing ANYONE to |
97 |
# execute malicious code after an exception is raised. |
98 |
#set debug = false |
99 |
|
100 |
# Logging configuration |
101 |
# Add additional loggers, handlers, formatters here |
102 |
# Uses python's logging config file format |
103 |
# http://docs.python.org/lib/logging-config-fileformat.html |
104 |
|
105 |
[loggers] |
106 |
keys = root, vigigraph, sqlalchemy, auth |
107 |
|
108 |
[handlers] |
109 |
keys = console |
110 |
|
111 |
[formatters] |
112 |
keys = generic |
113 |
|
114 |
# If you create additional loggers, add them as a key to [loggers] |
115 |
[logger_root] |
116 |
level = INFO |
117 |
handlers = console |
118 |
|
119 |
[logger_vigigraph] |
120 |
level = DEBUG |
121 |
handlers = |
122 |
qualname = vigigraph |
123 |
|
124 |
[logger_sqlalchemy] |
125 |
level = INFO |
126 |
handlers = |
127 |
qualname = sqlalchemy.engine |
128 |
# "level = INFO" logs SQL queries. |
129 |
# "level = DEBUG" logs SQL queries and results. |
130 |
# "level = WARN" logs neither. (Recommended for production systems.) |
131 |
|
132 |
|
133 |
# A logger for authentication, identification and authorization -- this is |
134 |
# repoze.who and repoze.what: |
135 |
[logger_auth] |
136 |
level = WARN |
137 |
handlers = |
138 |
qualname = auth |
139 |
|
140 |
# If you create additional handlers, add them as a key to [handlers] |
141 |
[handler_console] |
142 |
class = StreamHandler |
143 |
args = (sys.stderr,) |
144 |
level = NOTSET |
145 |
formatter = generic |
146 |
|
147 |
# If you create additional formatters, add them as a key to [formatters] |
148 |
[formatter_generic] |
149 |
format = %(asctime)s,%(msecs)03d %(levelname)-5.5s [%(name)s] %(message)s |
150 |
datefmt = %H:%M:%S |