> It's hard to judge well without the full source code, but the way you
> have it written seems more like that you're using the guix package
> declared in the channel rather than the user's guix. (if you weren't, I
> wouldn't expect file-append at all, but just something like
> "/home/hass-user/.co
Hello Attila,
>
> (simple-service
> 'home-assistant
> shepherd-root-service-type
> (list
> (shepherd-service
>(requirement '(file-systems networking guix-daemon))
>(provision '(home-assistant))
>(documentation "")
>;; TODO herd stop doesn't work. it leaves the process
>;
> I have a not yet running attempt of home assistant packaged, maybe you
> would like to have a stab at it?
thanks for the heads up, but i'm no expert of the python ecosystem. that's why
i decided to first try it this way, instead of attempting to package it.
also, HA is updated rather regularl
Hi Attila
> dear Guix,
>
> my ultimate goal is to run Home Assistant (a python based service)
> from Shepherd.
I have a not yet running attempt of home assistant packaged, maybe you
would like to have a stab at it?
> packaging it seems to be too much effort, so i looked into running it in a
> `
> I have no idea it this is the cause, but the immediate difference I see
> between the terminal (working) and shepherd service (not working) is the
> current working directory. In the former case it would be ~hass, in the
> latter case it would be /. Guix shell defaults to making CWD available
> i
Hello Attila,
Attila Lendvai writes:
> dear Guix,
>
> my ultimate goal is to run Home Assistant (a python based service) from
> Shepherd.
>
> packaging it seems to be too much effort, so i looked into running it in a
> `guix shell --container`. it works fine when done from the terminal:
>
> $
