Earlier quoted context omitted.
I've pip-install it in my homeserver (a small celeron with enough ram and storage) BUT I have a note to all HA users and devs: why the hell keep insisting on the WebUI for configuring, it's NOT reproducible nor simple. Oh, of course, for a casual user it's simple, unfortunately no casual users know about HA or how to physically integrate HA in a smart home, so the idea of making a generic end-user system it's a failu…
what?
It's a common issue in modern software: devs are so inhabited to use cloud stuff not knowing what's behind they are mentally unable to comprehend why doing so it's a totally absurd thing. Software MUST REPLICATE with easy, your home infra should be replicated from scratch without much more than booting a custom live. You shouldn't need to re-do the same step again. In *nix we have this concept since decades, those from Windows land simply do not understand because replication for them it's a myth.
Give NixOS or Guix System a try and you'll understand: your setup is just a single or few text files, a command read them and generate a new deploy for you. No need to traveling ever changing UIs by hand, no YAML hell.
At another level it's the same for those from stratis/mdraid/lvm/btrfs vs zfs. Zfs is done for the operation, as a storage should be, flexible, simple, effective, the others are a pile of CRAP those who develop them do not even recognize why, because they have no real idea of automation even if they are core devs of some very low level system stuff. Another example: "systemctl status something" is a CLI designed by some who have no idea of the real world needs, otherwise it would be "systemctl something status" because typically when you look for a service status you might want thereafter reload/restart/stop it, if not the word exchange does change nothing to you. These are the sign of devs born on Windows that have never go behind their desktop or someone else cloud service so they have no idea about how to build an infra.
For HA most of it's devs I suppose have no p.v. at home, or they have no personal automation to maximize self-consumption so they do not know how many lines of YAML and wasted time on their UI such design imply. Instead with "dumb end users" in mind, people who NEVER EVER use HA seriously simply because they lack too much knowledge even if someone gives the a ready made system, they focus on "visual code" like Node Red, augmenting them messiness level while still no option exists to establish sensor data retention and pruning, you need aside InfluxDB so another dependency for next to nothing and an issue at a time HA became just a part of a system with NO UI at all because to use InfluxDB you need for instance Grafana and so you entirely replace HA slick UI. In the end you have done A MONSTER to handle simple automation of many stuff due to wrong design ideas, while it could perfectly be a single simple app, HA itself, for instance exposed in python directly.
At some level many start to understand and from UIs they tend to REPL, from disappearing menus to "dashes", from widgets to NotebookUIs for some scientific software, LLM prompts and so on, but even with that most still have to understand a decades old IT principle.