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.

FeedDeck

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.

It wasn’t worse to begin with. I just wanted to add that this doesn’t have to be intentional and can still happen, due to bias or whatever.

The problem is, that it doesn’t even have to be “evil”. Most people make assumptions. If you notice or suspect a question carrying an assumption, I think it’s the right thing to clear things up. A yes or no is simply not enough if the whole premise of the question might be flawed.

That always makes me angry in court scenes in TV, although there it’s likely intentional and therefore your mentioned “evil question”. I hope that shit doesn’t fly in real courtrooms.

Not just scrollbars. Buttons, input fields, etc.

Dammit I sometimes have to search for elements I can interact with. Back in the day it was self explaining.

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 .

Of course. Great, another D in programming.

Maybe he also meant “dude, that saw is really metal”. Who knows what that saw has been capable of.

Fantastic movie. Also essentially a completely different genre than all the sequels.

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.

IIRC it had better performance than Prometheus. We also ditched Elasticsearch in favor of ClickHouse to keep up with log ingestion.