-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdevelopment.ini
169 lines (140 loc) · 5.08 KB
/
development.ini
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
#
# vigigraph - Pylons development environment configuration
#
# The %(here)s variable will be replaced with the parent directory of this file
#
# This file is for deployment specific config options -- other configuration
# that is always required for the app is done in the config directory,
# and generally should not be modified by end users.
[DEFAULT]
debug = true
# Uncomment and replace with the address which should receive any error reports
#email_to = [email protected]
smtp_server = localhost
error_email_from = paste@localhost
[server:main]
use = egg:Paste#http
host = 0.0.0.0
port = 8082
[app:main]
use = egg:vigilo-vigigraph
password_schemes=sha256_crypt
deprecated_password_schemes=hex_md5
lang=fr
help_link=http://foo.bar/help
cache_max_age=0
; URL vers laquelle l'icône "Maison" redirige.
; Les URLs partielles sont relatives à l'application
; (ex : "/" redirige vers la page principale de l'application).
;
; Utiliser une URL absolue pour pointer vers une autre application
; (ex : "http://example.com/").
home_link = /
app.vigicore = /
; Emplacement des applications (vigirrd, Nagios, ...)
; sur les serveurs distants.
app_path.vigirrd = /
app_path.nagios = /nagios/
; Schéma ("protocol") à utiliser pour se connecter
; à l'application. En général : http ou https.
; Par défaut : http
app_scheme.vigirrd = http
app_scheme.nagios = http
; Port de connexion au serveur distant hébergeant
; l'application.
; Par défaut : 80
app_port.vigirrd = 8084
app_port.nagios = 80
; Délai de rafraîchissement (en secondes)
refresh_delay = 30
; Liste des noms des groupes d'utilisateurs privilégiés,
; séparés par des virgules.
; Par défaut : "managers"
admin_groups = managers
full_stack = true
cache_dir = %(here)s/data
beaker.session.key = vigigraph
beaker.session.secret = vigilo
sa_auth.cookie_secret = vigilo
# If you'd like to fine-tune the individual locations of the cache data dirs
# for the Cache data, or the Session saves, un-comment the desired settings
# here:
#beaker.cache.data_dir = %(here)s/data/cache
#beaker.session.data_dir = %(here)s/data/sessions
# If you have sqlite, here's a simple default to get you started
# in development
sqlalchemy.url=postgresql://vigilo:[email protected]/vigilo
#sqlalchemy.url = sqlite:///%(here)s/devdata.db
#echo shouldn't be used together with the logging module.
sqlalchemy.echo = false
sqlalchemy.echo_pool = false
sqlalchemy.pool_recycle = 3600
# if you are using Mako and want to be able to reload
# the mako template from disk during the development phase
# you should say 'true' here
# This option is only used for mako templating engine
# WARNING: if you want to deploy your application using a zipped egg
# (ie: if your application's setup.py defines zip-safe=True, then you
# MUST put "false" for the production environment because there will
# be no disk and real files to compare time with.
# On the contrary if your application defines zip-safe=False and is
# deployed in an unzipped manner, then you can leave this option to true
templating.mako.reloadfromdisk = true
# the compiled template dir is a directory that must be readable by your
# webserver. It will be used to store the resulting templates once compiled
# by the TemplateLookup system.
# During development you generally don't need this option since paste's HTTP
# server will have access to you development directories, but in production
# you'll most certainly want to have apache or nginx to write in a directory
# that does not contain any source code in any form for obvious security reasons.
#
#templating.mako.compiled_templates_dir = /some/dir/where/webserver/has/access
# WARNING: *THE LINE BELOW MUST BE UNCOMMENTED ON A PRODUCTION ENVIRONMENT*
# Debug mode will enable the interactive debugging tool, allowing ANYONE to
# execute malicious code after an exception is raised.
#set debug = false
auth.config = %(here)s/who.ini
#auth.log_file = stdout
#auth.log_level = debug
# Logging configuration
# Add additional loggers, handlers, formatters here
# Uses python's logging config file format
# http://docs.python.org/lib/logging-config-fileformat.html
[loggers]
keys = root, vigigraph, sqlalchemy, auth
[handlers]
keys = console
[formatters]
keys = generic
# If you create additional loggers, add them as a key to [loggers]
[logger_root]
level = INFO
handlers = console
[logger_vigigraph]
level = DEBUG
handlers =
qualname = vigigraph
[logger_sqlalchemy]
level = INFO
handlers =
qualname = sqlalchemy.engine
# "level = INFO" logs SQL queries.
# "level = DEBUG" logs SQL queries and results.
# "level = WARN" logs neither. (Recommended for production systems.)
# A logger for authentication, identification and authorization -- this is
# repoze.who and repoze.what:
[logger_auth]
level = INFO
handlers =
qualname = auth
# If you create additional handlers, add them as a key to [handlers]
[handler_console]
class = StreamHandler
args = (sys.stderr,)
level = NOTSET
formatter = generic
# If you create additional formatters, add them as a key to [formatters]
[formatter_generic]
format = %(asctime)s,%(msecs)03d %(levelname)-5.5s [%(name)s] %(message)s
datefmt = %H:%M:%S
class = vigilo.common.logging.VigiloFormatter