It just previously avoided the bad optics of pulling a gun at their head, just so most people don’t know they’re hostages.

No, we all knew. And the optics were bad.

I use a local ntfy server and uptimekuma, which has built-in support for a ton of notification services, including ntfy.

You can also use the public ntfy server and create a topic there.

With multiple DNS servers and zone transfers.

Already a bunch of really good answers here, but I’ll add that I’ve wrestled with getting DBs to work well over NFS, and it’s doable, but you really, really have to know the particulars of sync on NFS and block settings on the filesystems and the db client/server at each end.

I collect GPS tracks (whenever I go somewhere I haven’t been, hiking included), and I also use wanderer for basic editing.

However, Wanderer has been trouble to upgrade and recently I’ve decided to just back up my Comaps tracks and export individual ones for editing on something like https://gpx.studio/. What I really need is a local version of comaps for big-screen visualization and planning.

How is Wanderer helping you?

Classless interdomain routing is not the point of this post, but basically we started giving people more options for network sizes, and while complex in implementation, it was philosophically virtually uncontroversial.

You’re talking about 2 different things here. Bit masking part of what is now CIDR was implementable since the mid 90s on network segments, it’s the logic to route packets based on CIDR that was integrated into RIP, GRIP, and BGP.

Also, CIDR can’t alleviate multi-hop routing address exhaustion.

They are saying wireguard alone, no reverse proxy. No exposing any services at all to the outside, just tunnel in with WG and access locally.

You realize dollar for dollar doesn’t mean retaliation with tariffs directly, right? There are other tools in the toolbox.

Radicale was easy enough for me. Davx5 on android to connect to it, and that’s it.

There is.

when it clearly should not be doing it.

No, sorry. We don’t know enough to say this. What were the options when configuring ext4? What record size is grafana using? Mariadb or postgres? Is there contention with another db? Is there a mounted NFS path in the same ext4 partition with weird block settings? There are lots of legitimate config reasons for op’s problem, but there are so many parts of op’s setup we don’t know, we similarly can’t possibly know what the issue is.

Swappiness works as intended in most default scheduler configurations and seeing high swap is a symptom, not an issue. It is almost always more productive to find out why the swapping is happening.

Not sure what you’re getting at with TRIM.

I agree that hitting swap is not ideal, but messing with swappiness sysctl is almost never the answer and very often leads to more problems than it solves.

If you want to tune for workload without needing fairly deep understanding of how Linux manages memory, use a sysctl that sets a whole system behaviour like CPU governor presets.

IMO, Linux is configured for “old” systems by default: slow HDDs, and constrained RAM pools, where disk IO really, really needs caching, and where idle background processes take a large fraction of RAM.

Not really a matter of opinion, and not true since kernel 5.1 when ssds became first class citizens.

Ooof, that domain name, tho…

Mangione has such a massive and popular following that there almost no way he is sentenced normally, it would be political suicide. The martyrdom alone would be hugely disruptive.

So, couple things here:

1. Most VPS have elastic memory, meaning they can borrow burst ram from the host for short periods. This means you 1GB vps can probably run at 1.5GB or even two during some demanding jobs for a short time. And depends on the provider.
2. You don’t document how you installed any of these.
3. .net core doesn’t work that way, it’s not “running” underneath the arr stack. There is some init stuff that happens when you first start a .net app, setting up DLLs, paths in /opt and such, but there isn’t a resident “layer” involved.
4. My arr stack executables never, ever exceed 700MB, 2GB is more than enough and pretty conservative. I’ve watched these metrics since the days when radarr and sonarr were backed by mono. You do need some mem space to store temporary show/movie metadata, but it’s trivial.
5. As others have said, peak demand is what you want to know, not base requirement.

Generally, I like where you’re taking this, but I think some more experience with how processes and memory work will help you a lot.

Opnsense is based on FreeBSD, not openbsd. They are different in handling jails, driver and fs support, so it does matter if you’re looking for info.

I appreciate your candor, but do you understand why the backlash happens?

One thing I wish ai would teach vibe coders is how to use semantic versioning.

Trying to infer state of project from versions in ai-assisted software is an exercise in confusion.

Agree on the Jonsbo. I have an N1 and it is not great for cooling HDD either. Jonsbo seem to design their cases as ideas and never actually test them.

I have found that a combo of Terraform and ansible cover almost everything, if that’s of any use.