mirror of
https://github.com/home-assistant/supervisor.git
synced 2025-12-24 12:29:08 +00:00
16b71a22d1
* Revert Home Assistant configuration to `/config` With the new add-on config feature the intention is to provide a good location for add-on specific configurations. Currently, add-ons such as Node RED or ESPHome use the Home Assistant config directory because this location is accessible to the user (via Samba VSCode add-on etc.). To make it clear to add-on developer that the new intention is to use add-on specific config, the implementation now bind mounts the add-on configuration directory to `/config`. And since some add-ons still need access to the Home Assistant configuration, its config folder is mounted to `/homeassistant` under the new scheme. However, users do know the path `/config`, and edit things e.g. through the SSH or VS Code add-on. Also `/config` is still the directory from inside the Core container. For SSH/VS Code add-on we could work around using a symlink, but that only works as long as these add-ons don't have a add-on config themselfs. This all has very high confusion potential, for not much gain. The renaming is mainly "developer friendly", but not really user friendly. Let's minimize potential confusion, and keep things where they are. The Home Assistant config directory stays at `/config, in all cases, everwhere. Map the new add-on configuration directory to `/addon_config`. * Adjust tests/comments