Oh huh, really? I thought Europe used calories.

Also by pure coincidence, Matt Colville released a video explicitly paying homage to Technology Connections the same day, too.

https://www.youtube.com/watch?v=RbfBhwkEQ_M

fwiw there’s a comment by @Mycatiskai@lemmy.ca as a top-level reply to the post that I think was intended as a reply to you.

kWh are a metric unit (even if they’re not SI), and are extremely common in discussions of household electricity. I wish it weren’t the case, the same way I wish countries other than Australia used kilojoules for measuring energy in food instead of (kilo)Calories. But they don’t.

I like it cos it lets you browse more sneakily at work.

Not exactly the same thing, but I used to have a terminal-based Reddit client, back before the API change put a kabush to that. Anyone know if there’s a simple text-based Lemmy or Piefed terminal client?

3 month? Wtf?

A lot of that’s still available in AOSP. The devices they actually sell just load a heap of commercial crap on top of that.

Oh good tip!

That’s a pretty righteous set up OP.

Lol not me. I’m not the author. Just saw the article and thought it was an interesting conversation starter.

or a recipe for an insecure mess that could become difficult to maintain

The concept, or the specific setup the author of that article has? If you mean the latter, I’m not going to argue. But the concept? It shouldn’t have any effect either way on security, but the whole advantage of it is that it’s less of a mess. The same way that running a whole bunch of services on bare metal can quickly become a mess compared to VMs or Docker/LX containers, declared state helps give a single source of truth for what all the services you might be running are. It lets you make changes in repeatable and clearly documented ways, so you can never be left wondering “how did I do that before?” if you need to do it again.

If everything you run is a Docker container, there’s a good chance Terraform is overkill; a Kubernetes config will probably do the job. But depending on your setup there are a whole bunch of different tools that might be useful.

What’s your preferred approach to defined state in your home servers?

It’s funny cos when I was young I recall it being called (at least sometimes) ADD. So the H has been added (or made mandatory in the name) at a time when we’re realising that hyperactivity is not a necessary symptom.

Oh, I used HA to mean high availability. I was not aware people also abbreviated Home Assistant.

Sorry for the late reply. I’m just disorganised and have way too many unread notifications.

LXC containers sound really interesting, especially on a machine that’s hosting a lot of services. But how available are they? One advantage of Docker is its ubiquity, with a lot of useful tools already built as Docker images. Does LXC have a similarly broad supply of images? Or else is it easy to create one yourself?

Re VM vs LXC, have I got this right? You generally use VMs only for things that are intermittently spun up, rather than services you keep running all the time, with a couple of exceptions like HomeAssistant? What’s the reason they’re an exception?

Possibly related: your examples are all that VMs get access to the discrete GPU, containers use the integrated GPU. Is there a particular reason for that distribution?

I’m really curious about the cluster thing too. How simple is that? Is it something where you could start out just using an old spare laptop, then later add a dedicated server and have it transparently expand the power of your server? Or is the advantage just around HA? Or something else?

Sorry for the late reply. I’m just disorganised and have way too many unread notifications.

LXC containers sound really interesting, especially on a machine that’s hosting a lot of services. But how available are they? One advantage of Docker is its ubiquity, with a lot of useful tools already built as Docker images. Does LXC have a similarly broad supply of images? Or another easy way to run things?

and MacOS

Oh that’s interesting. I wonder why they do it that way, considering macOS is a Unix OS.

Yeah I’m interested in how that works too.

I’ve recently been looking at the Nextcloud “all in one” Docker image. It works by mounting the docker.sock file into the master container, which allows that container to stand up a whole bunch of other containers on your machine.

How would that work on Windows, if the Docker socket isn’t a file handle?

That might be part of it, but I was thinking it was more how things we don’t think of as files, like sockets, are accessed with a file descriptor.

Oh yeah, the “run headless” tip too was great! I would never have used a desktop environment, and would in effect have been using it headless. But had you and others not specifically suggested running it as headless it would probably not have occurred to me that that’s a setting change I’d need to make while installing it.

Absolutely!