Usage of logging.default.yaml about smarthome HOT 7 CLOSED

When usinig SmartHomeNG without Docker, SmartHomeNG starts without any problems even if there is no etc/logging.yaml. In that case, etc/logging.yaml.default is copied to etc/logging.yaml SmartHomeNG starts as usual

It must be a problem in your (Docker-)configuration that prevents SmartHomeNG to copy the file.

from smarthome.

Thank you for the info. I will look in that direction

from smarthome.

I did some debugging. I think I got the bug:

I use a custom conf_dir with parameter --config_dir /mnt/conf

lib/smarthome.py Line 218 - 251 ensures, as you mention, all config files beeing copied from ".default". In my case for /mnt/conf (with /usr/local/smarthome/etc as source)
Important: self._etc_dir is modified in Line 237 to /mnt/conf.

However, Line 211 (earlier) a instance of Log is created, that reads etc_dir in Line 66 stil to /usr/local/smarthome/etc.

Later, when configure_logging is called, that is not updated.

I suggest to move Line 66 lazy into the function that need it, as it is mutable.

from smarthome.

master...AAPohl:smarthomeLoggingFix:master

It works with these modifications

from smarthome.

Fix looks basically fine, but absolutely not merging into master... ;). please create a new PR from a develop based branch to develop.

from smarthome.

Sorry for that. Made a new PR into develop

from smarthome.

Merged fix.

from smarthome.