HA is definitely the largest adopted. OpenHab is probably more geared for developers, but has a more concise and powerful automation system.
As for hardware to run it on: get a cheap n100 Minipc and be done with it. Uses 6-12W, and it’s going to miles.kore efficient for this use than a regular PC.
It’s not the CPU. All that will do is consume CPU and raise your energy bill.
In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.
When talking about media streaming, there’s a number of other things that cause problems Bandwidth, meaning the total amount of information you can send overall, is less likely to be a problem versus jitter, packet loss, and latency spikes.
For this purpose, but OP would tune both the server and the clients to cache ahead more, or send in smaller packets, it could possibly be a good workaround.
Spending an insane amount of money putting what I’m guessing is illegally obtained content on a CDN distribution is crazypants.
Bandwidth does not degrade over distance. That’s not how that works…
Again, I’m confused on what you’re suggesting the actual issue is here.
Uplink is exactly the problem. Not sure why you think otherwise. The internet doesn’t work by multicast.
You’re describing a CDN. You can’t afford it.
I’d look more into boosting whatever your uplink is versus trying to distribute to localized users.
Helm sucks. You don’t even need it for what you’re trying to do.
Mint is for desktops. Hands down.
Run something paired down for servers. Fedora Server, or plain Debian are fine. CoreOS or Talos if you’re trying out some k8s stuff.
Yes, it’s mostly just package selection, but you don’t need to sift through the cruft and clean up all the desktop shit running you don’t need.
Docs say you can choose what to sync, and disable syncing entirely where you don’t want it: https://docs.nextcloud.com/server/latest/user_manual/en/desktop/usage.html
Pretty sure you should have the ability to choose what to sync, either from the server, or the client. Seems kind of dumb for it to automatically assume you have the space on the client device to sync EVERYTHING.
Well, firstly, it’s not what Tailscale is meant for. I’m getting downvoted by the people using the wrong tool for the wrong job.
You don’t install a VPN on all your local machines just to talk to each other. That’s insane. You especially don’t install one that, while misconfigured, is sending all of its traffic OUTSIDE of your local network, then back in. This is what Tailscale on a number of local machines will do by default.
The way Tailscale works is by installing a Wireguard client on a machine. It then checks in with their DERP servers to figure out it’s network situation (behind NAT, peers in the network, routing tables…etc). So when you have more than one client on the Tailscale network, it automagically assumes some things, the first being that these two machines dont have a more direct route to talk to each other.
So then it will attempt to bridge a path between the DERP server each client is checked into, and pass traffic that way. Which means you then have two machines on the same local network sending traffic OUTSIDE of that network, then back in to complete a VPN network.
This is stupid.
You setup multiple different networks and use exit nodes to bridge two networks together with Tailscale. That’s the entire point. This means setting up routes to let the orchestration layer know that a set of certain machines exist in the same network, and shouldn’t use Tailscale to communicate with each other. Then it will only be using routes for REMOTE networks, where other clients exist, to pass traffic over the Tailscale network.
May I ask what you were planning on doing with Tailscale? I can point you in the right direction.
https://gist.github.com/camullen/0c41d989ac2ad7a89e75eb3be0f8fb16
Just cut Windows out as much as possible and run everything in WSL. Setup everything to boot straight to all your WSL layers, and aside from the absolute shit Base OS, it should be the same.
Move your Nginx pets to something else. Pretty simple.
Okay, but give a little look into where your disk is using space.
du -hsc /
And work from there.
It depends on where that storage was used. Some details would be useful.
At its core, you shouldn’t need to keep any previous layers than the one you’re using for the OS.
You also technically don’t need snapshots for anything but your personal file space.
I’m not sure what you’d like here. You didn’t give much info.
Did you want someone to literally work out a full config for you in here? We don’t know what you’re even running.
This is just basic network routing and subnetting.
Not sure what the Frame means with any of this. It’s going to be running the same stack as Deck, which is KDE. It’s also not going to be any sort of headset for your PC, at least at the outset.
As for your other Dr questions, it’s all just personal preference. The Desktop is just window dressing on a compositor and window manager anymore. If you’re comfortable without all the system helpers and convenience of using either Gnome or KDE, you can just run a WM like Hyprland or Sway instead.
If you’re going for reliability, and you just want things to be simple, you probably just want to spend the money on two cheap NAS boxes, honestly. There are some caveats that come with RPi’s, and you’re unfamiliar it’s: 1) going to cost about the same, 2) be simpler to manage and upgrade, and 3) be easier to repair disk columes when the time comes.
Even if you’re just looking to make these redundant to each other, just make it simple and easy.