Configuration directory about architecture

[rytilahti]

Generally speaking I like the idea of using standardized locations for files. OSX has its own structure for storing these files, see https://github.com/ActiveState/appdirs for a library to obtain the proper directory for a specific data type on all common platforms.

So on a generic linux the data locations would be something like this:

• ~/.config/home-assistant/ for configuration
• ~/.cache/home-assistant/log/ for logs
• ~/.cache/home-assistant/deps/ for cached dependencies
• ~/.local/share/home-assistant/ for data files (www, custom_components should belong here I think)

The question I have is that converting it all backwards compatible to this format would require some work, and "reseting" ones installation will be more complicated than "please remove ~/.homeassistant/", is it still worth the effort and what pros & cons there are for doing this?

[dgomes]

HomeAssistant runs as a daemon, why keep everything in a home dir ?

IMHO it should be moved to the POSIX etc dir.

Since many people run HA inside a container, splitting the configuration throughout several subtrees is also a less then optimal idea.

BTW: I find this issue of very low priority.

[frenck]

This architecture issue is old, stale, and possibly obsolete. Things changed a lot over the years. Additionally, we have been moving to discussions for these architectural discussions.

For that reason, I'm going to close this issue.

../Frenck