- 0 Posts
- 23 Comments
Mostly a nitpick, but for that little helper I would have stuck to the stdlib and not pulled in a dependency like echo.
Otherwise: nice idea. I did something similar but since caddy runs directly on my host, I added permissions for the other services that need the cert and then pointed them directly at it.
I am surprised that no one mentioned snikket yet, which is essentially a distribution of Prosody with sane defaults and a custom client.
The bigger issue (IMO) is, that you now have a hard requirement on the startup order of your services. If another one happens to get the IP assigned automatically befor your service starts that requests it explicitly, you now have a conflict that you manually have to resolve.
DNS is the only sane solution here.
But everyone does keep their license. A company can not really take over in the sense that you lose your old code. They can stop developing in public but keep using your code, but so can you keep using the last public version and keep developing it. Or you can take your contribution and apply it elsewhere.
Of course. Great, another D in programming.
My point however was that people who want that kind of convenience (or rather who don’t want to fiddle around manually), why would they want to run HASS in a container in the first place? Either you are tinkerer, then it doesn’t matter or you are not, in which case you probably don’t arrive at the point of running HASS on anything other than a preinstalled distro in the first place.
When I host multiple services, I need to back them up as well. I simply mount all data volumes of all containers into a unified location that gets backed up by kopia every hour.
Since the volume is directly on disk, I also didn’t have any problems editing configuration files.
The things I see listed as addons on the website are dedicated services anyway, that have images of their own you can easily spin up as containers.
I think if someone is advanced enough to want to run HASS on their own together with other stuff, they prefer to have more control anyway.
Strip prefix won’t work if the frontend expects to find paths at absolute locations. You would need to patch the html, css and js on the fly, which is somewhere between ugly and (almost) impossible.
I would also suggest to simply use custom (sub) domains. Especially in your intranet you can have whatever domains you want.
I don’t believe in this distinction. I am proud of my work. If I wasn’t, I would have almost no drive to deliver good or even any results. I like what I do.
So of course it becomes a difference if you tell me that there is a better way to do what I did (aka giving me something to improve) or if you tell me that my work is utter crap (aka taking away any positivity I had).
So yes, my code can be wrong or bad. But it’s still something I produced. So I prefer to not have it treated like a piece of shit.
So “it’s weird then”. As I said. And basically as the person I answered to said.