vigigraph / development.ini @ 4cdb7492
History | View | Annotate | Download (4.15 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 |
full_stack = true |
25 |
#lang = ru |
26 |
cache_dir = %(here)s/data |
27 |
beaker.session.key = vigigraph |
28 |
beaker.session.secret = somesecret |
29 |
|
30 |
# If you'd like to fine-tune the individual locations of the cache data dirs |
31 |
# for the Cache data, or the Session saves, un-comment the desired settings |
32 |
# here: |
33 |
#beaker.cache.data_dir = %(here)s/data/cache |
34 |
#beaker.session.data_dir = %(here)s/data/sessions |
35 |
|
36 |
# pick the form for your database |
37 |
# %(here) may include a ':' character on Windows environments; this can |
38 |
# invalidate the URI when specifying a SQLite db via path name |
39 |
# sqlalchemy.url=postgres://username:password@hostname:port/databasename |
40 |
# sqlalchemy.url=mysql://username:password@hostname:port/databasename |
41 |
|
42 |
|
43 |
# If you have sqlite, here's a simple default to get you started |
44 |
# in development |
45 |
|
46 |
sqlalchemy.url = sqlite:///%(here)s/devdata.db |
47 |
#echo shouldn't be used together with the logging module. |
48 |
sqlalchemy.echo = false |
49 |
sqlalchemy.echo_pool = false |
50 |
sqlalchemy.pool_recycle = 3600 |
51 |
|
52 |
# if you are using Mako and want to be able to reload |
53 |
# the mako template from disk during the development phase |
54 |
# you should say 'true' here |
55 |
# This option is only used for mako templating engine |
56 |
# WARNING: if you want to deploy your application using a zipped egg |
57 |
# (ie: if your application's setup.py defines zip-safe=True, then you |
58 |
# MUST put "false" for the production environment because there will |
59 |
# be no disk and real files to compare time with. |
60 |
# On the contrary if your application defines zip-safe=False and is |
61 |
# deployed in an unzipped manner, then you can leave this option to true |
62 |
templating.mako.reloadfromdisk = true |
63 |
|
64 |
# the compiled template dir is a directory that must be readable by your |
65 |
# webserver. It will be used to store the resulting templates once compiled |
66 |
# by the TemplateLookup system. |
67 |
# During development you generally don't need this option since paste's HTTP |
68 |
# server will have access to you development directories, but in production |
69 |
# you'll most certainly want to have apache or nginx to write in a directory |
70 |
# that does not contain any source code in any form for obvious security reasons. |
71 |
# |
72 |
#templating.mako.compiled_templates_dir = /some/dir/where/webserver/has/access |
73 |
|
74 |
# WARNING: *THE LINE BELOW MUST BE UNCOMMENTED ON A PRODUCTION ENVIRONMENT* |
75 |
# Debug mode will enable the interactive debugging tool, allowing ANYONE to |
76 |
# execute malicious code after an exception is raised. |
77 |
#set debug = false |
78 |
|
79 |
# Logging configuration |
80 |
# Add additional loggers, handlers, formatters here |
81 |
# Uses python's logging config file format |
82 |
# http://docs.python.org/lib/logging-config-fileformat.html |
83 |
|
84 |
[loggers] |
85 |
keys = root, vigigraph, sqlalchemy, auth |
86 |
|
87 |
[handlers] |
88 |
keys = console |
89 |
|
90 |
[formatters] |
91 |
keys = generic |
92 |
|
93 |
# If you create additional loggers, add them as a key to [loggers] |
94 |
[logger_root] |
95 |
level = INFO |
96 |
handlers = console |
97 |
|
98 |
[logger_vigigraph] |
99 |
level = DEBUG |
100 |
handlers = |
101 |
qualname = vigigraph |
102 |
|
103 |
[logger_sqlalchemy] |
104 |
level = INFO |
105 |
handlers = |
106 |
qualname = sqlalchemy.engine |
107 |
# "level = INFO" logs SQL queries. |
108 |
# "level = DEBUG" logs SQL queries and results. |
109 |
# "level = WARN" logs neither. (Recommended for production systems.) |
110 |
|
111 |
|
112 |
# A logger for authentication, identification and authorization -- this is |
113 |
# repoze.who and repoze.what: |
114 |
[logger_auth] |
115 |
level = WARN |
116 |
handlers = |
117 |
qualname = auth |
118 |
|
119 |
# If you create additional handlers, add them as a key to [handlers] |
120 |
[handler_console] |
121 |
class = StreamHandler |
122 |
args = (sys.stderr,) |
123 |
level = NOTSET |
124 |
formatter = generic |
125 |
|
126 |
# If you create additional formatters, add them as a key to [formatters] |
127 |
[formatter_generic] |
128 |
format = %(asctime)s,%(msecs)03d %(levelname)-5.5s [%(name)s] %(message)s |
129 |
datefmt = %H:%M:%S |