....appconfig is the tool, you are the brain. Everyone has its own
preferences.
Personally I use a post-deployment step to fiddle with settings, as
DEPLOYment is not DEVELOPment.
You can use a SINGLE env variable to switch configs
prod_conf = os.environ('isthisprod')
if prod_conf:
myconf = AppConfig(prod_conf)
else:
myconf = AppConfig(another_path, reload=True)
and I don't see any issues with it. AppConfig is built for speed. There's
absolutely no logic in it.
If you want to concoct your own module for the "merge-inheritance" issue,
code your own.
AppConfig is less than 100 LOC.
BTW: use .take() for production. get() is just a waste of cpu, useful only
for development.
On Friday, April 15, 2016 at 5:54:30 PM UTC+2, pbreit wrote:
>
> Even better would be some sort of inheritance so you only end up
> overriding a handful of settings in production.
>
> Was this intended for that or should I be looking elsewhere?
>
> On Friday, April 15, 2016 at 8:25:54 AM UTC-7, pbreit wrote:
>>
>> But is there a good or proscribed way to use AppConfig for Dev and Prod
>> settings?
>>
>> If I do JSON can I do something like:
>>
>> {
>> "dev": {
>> "db": sqlite
>> }
>> "live": {
>> "db": postgres
>> }
>> }
>>
>> and then something like:
>>
>> if is_local:
>> myconf = AppConfig(reload=True)['dev']
>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
