Re: _cpconfig.py - staging ~ production environments

On Nov 25, 10:04 am, "Robert Brewer" <fuman...@...> wrote:
> dundeemt wrote:
> > Wondering why the 'staging' environment has autoreload and other
> > logging turned off by default
>
> >http://www.cherrypy.org/browser/trunk/cherrypy/_cpconfig.py#L108
>
> > note how staging and production only differ with production adding the
> > log.screen:False option
> > 106        environments = {
> > 107            "staging": {
> > 108                'engine.autoreload_on': False,
> > 109                'checker.on': False,
> > 110                'tools.log_headers.on': False,
> > 111                'request.show_tracebacks': False,
> > 112                },
> > 113            "production": {
> > 114                'engine.autoreload_on': False,
> > 115                'checker.on': False,
> > 116                'tools.log_headers.on': False,
> > 117                'request.show_tracebacks': False,
> > 118                'log.screen': False,
> > 119                },
>
> > Am I misinterpreting what 'staging' means in this context?  Are
> > environments kind of a "left-over" being overtaken by site.conf and
> > app.conf?
>
> No; environments are like "macros" for config. The staging environment