zlacker

>>pictur+(OP)
Can someone explain the Home Assistant anecdote regarding JS and curl | sudo sh? Does the author mean Home Assistant isn't secure? Or that there's some issue with the front end of it? Or something else?

Because imo... that is the answer. We have seen so many stupid closed ecosystems of home automation stuff come and go, I dunno why you'd mess with anything else at this point. In fact I just got another email reminder that Google is turning off the old Works with Nest stack. Remember Nest? Yeah...

>>jmuguy+Ey
The author is referring to the officially recommended way to install home-assistant on a Linux box, which is just curl-ing and running an install script as root.

I totally get how that's off-putting, but the real recommended way to run home assistant is to install Home Assistant OS on dedicated hardware. Which also can be off-putting.

Either way, it's my favourite software that I regularly interact with (unless you count Linux).

>>rpgwai+Vz
I don't think that's really fair - the recommended way to run Home Assistant is to run HA OS (on a VM or dedicated machine, like a Raspberry Pi), or to run it in a Docker container.

The "Supervised" installation (i.e. installing Home Assistant on top of an existing Linux install) is doable, but not preferred.

https://www.home-assistant.io/installation/

>>johnma+BD
Iirc they explicitly say don’t / recommend against it. I mean I still did but it definitely isn’t the way most people will install it at all

>>katbyt+1G
We tried, but the community wanted to keep the installation method, so we kept it around.

>>raman3+VM
personally i did it because i like my servers to be debian & i wanted it to match all the other VMs i have running

so thanks for keeping it around :)