“It’s just a temporary fix.”

…Five Years Later…

The painted pole is still there but the clock is gone.

In this situation it’s not necessarily that it’s the “right” or “wrong” device. The better question is, “does it meet your needs?” There are pros and cons to running each service in its own VM. One of the cons is the overhead consumed by the VM OS. Sometimes that’s a necessary sacrifice.

Some of the advantages of running a system like Proxmox are that it’s easily scalable and you’re not locked into specific hardware. If your current Beelink doesn’t prove to be enough, you can just add another one to the cluster or add a different host and Proxmox doesn’t care what it is.

TLDR: it’s adequate until it’s not. When it’s not, it’s an easy fix.

Yeah, with something that size you’re pretty much limited to containers.

Edit: Which is totally fine, OP. Self hosting is an opportunity to learn and your setup can be easily changed as your needs change over time.

I use one VM per service. WAN facing services, of which I only have a couple, are on a separate DMZ subnet and are firewalled off from the LAN.

It’s probably little overkill for a self hosted setup but I have enough server resources, experience, and paranoia to support it.

Anything but Hyper-V.

Broadcom’s management trying to spin lack of implementations as an opportunity when really it be more like:

I love my Remarkable 2. It’s a notebook that allows me to search through my notes and also doubles as an e-reader.

No web browser. No other unnecessary features. Just notes, documents, and books.

10/10.

To people who had never known any other way to travel than on foot, the horse was a major upgrade. To people accustomed to mechanized transportation, the horse is a major downgrade. Maintenance costs are one thing but the time requirements are what really makes it not affordable.

Current conditions in the US aside, Mississippi is just soy beans, mosquitoes, and poverty. It’s a shithole.

Serenity now! Serenity now!!

You’re getting job interviews?

Last time I had to track time it was on a shitty spreadsheet that had to be printed out and signed by my boss. I was salaried. There were usually no changes from week to week.

They also had a digital time tracking solution that they just refused to use because that would involve change and change is bad.

Return to office mandate and a slice of cold pizza.

In my previous team, we had a structure with four levels of nesting

Those are rookie numbers.

The query speed isn’t quite there but I would say it’s close enough for a lot of purposes, especially with proper indexing. And JSON column fields are indexable. Two things I’ve used Postgres’ JSON functionality for are:

1.) Storing unstructured data. 2.) Storing structured data that would exceed the table column limit.

In both cases, I’ve typically needed to extract the relevant data from the JSON records to either be stored in another table of turned into a materialized view so live query performance on the JSON columns was not that important.

Every time I’m assigned to a project that uses a document database

“So how are you guys handling all your related data?”

Finds collection of massive JSON documents containing all the related data

“Oh boy.”

Same. Poor decision on my part. 🙁

That’s the entire premise for Snapchat. And yes, it’s fucking weird.

I had an 06 Ford Ranger (actually a Mazda). RWD with a 4 cylinder and a 5 speed. No frills at all. That was a phenomenal truck. You could put snow tires on it, throw some sand bags in the bed, and go just about anywhere.

Letting Elmo & Co. anywhere near anyone’s critical infrastructure would be one of the stupidest ideas ever.