Thank you Jim, this approach worked for me.
If found out that the Apache directive
SetEnv KEY VALUE
is reflected in webpy via web.ctx.environ['KEY'] ... however this dictionary
only exists if a HTTP request is made, so it is useless for configuration BEFORE
any request happens. That is a pity, but I wonder if there is in general a way
around it.
Bests,
Dragan
Am 15.10.2013 05:54, schrieb Jim Gregory:
> I just create two config.py files, one for the local development server and
> one for production, and store all the variables unique to each environment in
> each file. I then import the file into code when I need server-specific
> parameters.
>
--
http://1x-upon.com/~despens/ >NEW!<
http://noobz.cc/
http://contemporary-home-computing.org/1tb/
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/webpy.
For more options, visit https://groups.google.com/groups/opt_out.
