So they have two airflows? Then I assume in contrast to the ones with just one exhaust they need two fans? One for circulating (and cooling) the air from the room and one to circulate the air from (and to) the outside?
Then I assume that would make them even noisier then the single exhaust ones, right? (More moving parts.)
Two tubes still means it pulls in hot air from the outside that it then needs to cool down first. The split ACs are basically the only sane ones (but expensive).
So “it’s weird then”. As I said. And basically as the person I answered to said.
Yeah but why not both? Extra support shouldn’t hurt.
… each time the server restart and randomly during login.
They already accept donations as a means of continuous support. So I guess this is now just another channel for people who prefer buying a license over using github donations.
Edit: oh I just realized they stopped donations with the restructuring. Ok, that’s weird then.
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.
If the AppleTV allowed side loading, it would be my dream device. The UX and the speed of Apple devices are just so damn pleasing. But the artificial limits they impose on what you can run on them is damn frustrating.
SiYuan is an opensource Notion alternative. (Not a clone.)
Lookup if the device is supported by LocalTuya though.
I made the mistake thinking that LocalTuya somehow acts like a proxy for a generic protocol, but it actually needs to understand the devices. Now I have a doorbell I can’t use with it.
I am surprised that no one mentioned snikket yet, which is essentially a distribution of Prosody with sane defaults and a custom client.
I meant DNS within your container network. Exposed stuff should be mapped to host ports.
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.
Tbf, systemd also makes it relatively easy to sandbox processes. But it’s opt-in, while for containers it’s opt-out.
Props for spelling “spelling” wrong in the title .
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.
Now I am intrigued to develop one that is called YOLO.
But just in case: no, I don’t monitor my server. If I notice something not working, I ssh into the machine and check what’s up. I don’t want to deal with another zoo of services for the monitoring part.
Thanks for filling that gap of knowledge!