4 ms·
Depends on how you're running it. When I was running hass.io on a RaPi, I used a few of those plugins (including PiHole). Now that I'm running HA in a VM on a b
by organsnyder 7y ago
Depends on how you're running it. When I was running hass.io on a RaPi, I used a few of those plugins (including PiHole). Now that I'm running HA in a VM on a bigger machine, it makes more sense to run those services as separate VMs alongside it.
- hunter2_ 7y agoI've been trying to decide between these options myself. I was never happy with the slow restarts and potential for microSD failure when I ran HA on a RaPi3 (years ago, legacy AIO on stock Raspbian) so I haven't kept up with it and now want to start from scratch on something like a NUC. Do I make Hass.io a VM along side other VMs for PiHole, my LAMP website, etc? It will be idle so much that low power/heat during idle is significantly important, but I love the simplicity of reverting an isolated service back to a snapshot after I break it. I suspect a single OS on metal with each of these in a Docker container would be more efficient, but I haven't played with containers before.
- organsnyder 7y agoI have a single machine running FreeNAS that's running all of my home services at the moment (I know it's not the best hypervisor, but I wanted my NAS on bare metal and I can't justify a separate dedicated server). I have Ubuntu running in a VM running Docker, and installed Home Assistant using the official instructions for this setup[1]. PiHole is so light-weight and relatively low-risk, you could easily run it on the same VM as Home Assistant if you'd like. I keep separate VMs for everything out of habit. I would isolate the LAMP site as much as possible, especially if it's publicly available—potentially even keeping it off of the same network as everything else. [1] https://www.home-assistant.io/docs/installation/docker/ https://www.home-assistant.io/docs/installation/docker/