pip upgrading breaks the former installed configuration

[mohierf]

When upgrading the web ui with the pip install alignak-webui --upgrade the former configuration is replaced with the default shipped configuration.

This is the drawbacks of pip distributing this application :/

Perharps we should ship settings.dist, logging.dist and uwsgi.dist to be renamed by the end user as settings.cfg, logging.json and uwsgi.ini ... this will avoid deleting a real configuration when upgrading

[mohierf]

Moreover, upgrading is always destroying the existing log files because the /usr/local/var/log/alignak-webui directory is deleted during the uninstall process (same as the configuration files directory).

Currently it does not look possible to interfere with the pip uninstall process and thus avoid files deletion!

[mohierf]

The proposed solution (to be tested). Oon start, the Web UI application:

• checks whether required directories exist. If not they are created
• checks whether a configuration file is found. If the file is found, the application starts with this configuration
• If no configuration file exists, the application will copy a settings.dist file to settings.cfg as a default configuration file

The problem that is not fixed with this solution is the uwsgi.ini file ... let's assume that the sysadmin will be able to copy an uwsgi.dist file to uwsgi.ini 😉