WebUI logging strategy

[mohierf]

The WebUI uses a Python logger to make its log. furthermore, the uWSGI also makes its own log.

As a result,we may have several log files:

• [ ] webui-access.log, from uWSGI, that will contain the uWSGI HTTP requests
• [ ] webui-error.log, from uWSGI, that will contain the WebUI console log
• [ ] info.log, from WebUI, that will contain the INFO level log
• [ ] warning.log, from WebUI, that will contain the WARNING level log
• [ ] error.log, from WebUI, that will contain the ERROR level log

After some experiments, the 3 last configured files are not really interesting. Only both first files are pertinent. As such, I will make a default configuration with only the uWSGI log files activated.

Changing the application log level is done thanks to the logging.json file or an environment variable to set the application DEBUG mode.

[mohierf]

I re-open this issue because of #191 ... perharps that the WebUI should only rely on the Python logging and do not care about what uWSGI will decided for the log. Setting a configuration in the default logging.json file that produces one daily rotated log file should be a good strategy ...