Open traylenator opened 2 years ago
Although quite much of the HomeAssistant state and configuration is outside Puppet, this module does seem to be useful for me.
This puppet module puts the configuration under /etc/homeassistant
, and that's where I think it belongs. Unfortunately, it also puts quite some state and even log files under the same directory. I think the problem is that the upstream HomeAssistant project is not good enough at separating "configuration" and "state" (and to some extent, even code).
If one considers things like user management (stored under /etc/homeassistant/.storage/auth_provider.homeassistant
) to be "state" rather than "configuration", then it's perfectly OK that the puppet module doesn't handle it.
I've been through some rounds of installing/migrating HomeAssistant, this is the first time I try to do things via Puppet. Some notes:
pacman -S home-assistant
on Archlinux. I'm quite unhappy about the results, got a relatively old version of HomeAssistant, and the particularly the location of configuration files (/var/lib/hass/
, but there is again a symlink to /var/lib/private/hass
, and the /var/lib/private
is supposed to be accessible only by root - making it hard to maintain configuration files manually).
This module should be archived.
It's a long time since home assistant could be configured purely with yaml and as such this module is useless I believe.