What happened to librem anyway? They used to be all the rage, now it’s nothing.

So, you fucked up and it’s postgres’ fault?

You could easily throw the components into an old tower case.

Getting the PSU to fit could be a bit tricky due to the rather short cables.

Workstations, like real workstations, are another beast and not what’s typically referred to as “office PCs”, those are indeed rather sff builds.

Again, optiplex sff 3060 as an example, it has two SATA ports, one x16 and one x1 (I think) PCIe, and looking at the PCB, apparently there’s a version with m.2 slots. Sure, not exactly server grade storage, but if you manage to find some version with m.2 slots or invest 10€ for a cheap SATA card, you can get enough storage attached.

GPU wise, absolutely no idea. My optiplex has a wx3100 that I got for cheap and its self reported power draw never goes under 5W, but since this machine is a desktop, it doesn’t run all day.

Sorry, but you’re either pulling those numbers out of your ass or haven’t kept up with the real world for 25 years.

The numbers I’ve posted above are measured using an external meter. I’m German, I have a vested interest in knowing how much power my devices pull.

And you don’t think, office PCs pay attention to power consumption, given they are intended to run 8h a day?

My optiplex sff runs at about 10-15W in idle, and it’s an i5 6500. The t variant in my elitedesk runs at 5W.

If you don’t need actually public DNS, something like Tailscale might be an option.

Because you don’t know what you’ll need that wrapper beforehand, that’s my entire point.

Unless you’re only doing trivial changes, the chances are very high that you won’t be able to design the class structure. Or, you end up essentially writing the code to be able to write the tests, which kind of defeats the purpose.

If you have to ask “can’t you just” the answer is almost always no.

And who actually writes tests like that?

I mean, do you think tests do the calculations again? You simply have well defined input and known, static output. That’s it.

Tests first is only good in theory.

Unit tests typically test rather fine grained, but coming up with the structure of the grain is 80% of the work. Often enough you end up with code that’s structured differently than initially thought, because it turns out that this one class needs to be wrapped, and this annotation doesn’t play nice with the other one when used on the same class, etc etc.

Especially then I’d test the shit out of everything? I’m getting paid for writing correct software.

For local development, it should be super quick. However, I’m currently building a small project where a device (or rather the library using it) can’t really be used with a debugger. So 500 print()s it is.

I find it extremely frustrating how weirdly wrong-density much documentation is. It’s extremely detailed in all the wrong places and often lacks examples for common use cases.

I learned a while ago that news articles are supposed to have increasing levels of detail from top to bottom. Each paragraph adds a bit more context, but the general picture should be contained in the first one. Hardly any documentation follows that pattern.

Ansible is actually pretty nice, if you get the hang of it. Not perfect, but better than triple tunnel ssh.

You could simply automate step by step, each time you change something, you add that to the playbook and over time you should end up with a good setup.

Flakey dev setups are productivity killers.

The real question is why you’re torturing yourself by manually fixing that stuff? Don’t you terraform your Ansibles?

None. There is no model that can output anything even remotely usable on that tiny amount of RAM and certainly not using the few CPU cycles your vps has to offer.

The US default, that I never left Europe. What an achievement for the USA!

Oh come on, are you really that boneheaded not to understand that you’re not the norm?

I literally had not a single power surge in my entire life. The only power outages I had were for a few minutes maybe three times in the last 15 years.

The larping refers to you. Either you are truly an outlier who actually runs a small DC, or you just like the feeling you can get pretending to do so.

Your attitude is roughly the “only gold plated cables made from solid silver” equivalent in audiophiles. Technically maybe correct, practically a self-important waste of money.

But not for us.

That’s what I meant by larping. The vast vast majority of us here would probably not even notice if their systems went down for an hour. Yes, battery backup has its purpose. In a datacenter.

I mean, what’s on the line here in the worst case? 15min without jellyfin and home assistant? Does that warrant taking risks with old batteries or investing in new ones?

That equation might change if you’re in a place with truly unreliable electricity, but I guess those places have solutions in place already.