##// END OF EJS Templates
scm-app: allow to set documented pyro4 as scm_app_implementation....
scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app

File last commit:

r271:401985cc default
r632:064401fe default
Show More
dev-settings.rst
46 lines | 959 B | text/x-rst | RstLexer
project: added all source files and assets
r1
==========================
Settings for Development
==========================
We have a few settings which are intended to be used only for development
purposes. This section contains an overview of them.
`debug_style`
=============
Enables the section "Style" in the application. This section provides an
docs: updates to contributor documentation #4039
r271 overview of all components which are found in the frontend of the
project: added all source files and assets
r1 application.
`vcs.start_server`
==================
Starts the server as a subprocess while the system comes up. Intended usage is
to ease development.
`[logging]`
===========
docs: updates to contributor documentation #4039
r271 Use this to configure logging to your current needs. The documentation of
Python's `logging` module explains all of the details. The following snippets
are useful for day to day development work.
project: added all source files and assets
r1
Mute SQL output
---------------
They come out of the package `sqlalchemy.engine`::
[logger_sqlalchemy]
level = WARNING
handlers = console_sql
qualname = sqlalchemy.engine
propagate = 0