All the same. There will be no appreciable difference in any of them at the level you’re interested that can’t be tweaked and tuned from the apps you use.
Edit: though if you want long running game servers, a small minipc that draws a tiny amount of power is a good way to continuously keep the server portion running without wasting a ton of energy. The Intel N100 or the Ryzen 5 (forget which) can both run below 12W, which is about the same as an LED light bulb.
I have this moon here if you’d like it?
VERY interesting. I don’t know why WSL is the pinning point for this, but I assume M$ needs this and they got paid a bounty (hopefully).
M$ is seriously trying to shift their shit Windows build systems over to WSL for some reason. It makes zero fucking sense. I bet this has something to do with that and replicating the success of GitHub Actions toolkit but a hat on a hat with Windows as the Bottom Bitch.
Pretty sad.
Nobody is going to touch that. Make builds available from a gitrepo maybe
Pretty much got it. Any other static routes you setup will be static to the new router only, but otherwise that’s pretty much it. Devices with static IPs don’t participate in DHCP, so it won’t cause a conflict. Just make sure DHCP is disabled on the new device.
You can decrease the timeout of the devices to maybe get them to show as offline faster. Thread about it here.
The default gateway for the new device needs to be your existing router in order to get to the internet. Then when you create a new WG connection, you ensure all traffic that gets passed to this new device forwards through the Wire guard tunnel.
PC > WG-router > existing-router > internet
You need a router or a proxy. A proxy would be annoying, so a router is preferred.
If you don’t have control of your edge router, just get a cheap Pi-type device, install OpenWRT, setup your VPN connections, then create a route on your network to point at this new device for whatever you need it for.
If you simply want to use it at-will for certain things, you can put a proxy on it.
As to your other issues, it sounds like your WG connection is just dropping, in which case it won’t automatically reconnect by default. OpenWRT has plugins that can monitor that and reconnect when it drops, or you can script it pretty quickly as well.
You don’t. If they don’t have power, they drop from the network or mesh.
This is why they make “Smart” Switches, which is probably more why you want instead of individual bulbs maybe.
You have an external HDD, so just use it as a temporary shuttle for your files if you don’t have enough space on your SSD to make it all fit comfortably.
I’ve never seen this “just” happen, but have seen it during events like switching from headphones to speakers and such.
You may also have your app volumes linked to your master channels, meaning when you lower the sound on your master with something like a key combo, then it lowers the individual app volumes as well, which is generally not something you’d want enabled.
Apps at full, and using PCM/Master channel for general volume is pretty much the “default”.
Literally explained in the link.
Unless there is an above average drive controller on board, it wouldn’t be getting out into read-only and still accessible without triggering an error in online drive checks.
Check your drive: https://wiki.archlinux.org/title/S.M.A.R.T.
This is a cm2002 post, so most assuredly not their project, but some notes:
Pruning clears cached blobs and unlinked objects. It 100% will not clear history unless you’re forcing a specific depth to be achieved, which, again, is not something that people who want a functional repo would do.
Mirroring is exactly that: a copy
If the thing you are mirroring does something you don’t like, you can’t stop. Literally imagine standing in front of a mirror and trying to stop the reflection from doing something you don’t like. Not happening.
The thing about git is that it keeps all history, even in a force push situation, unless they actively clear previous history, which is… difficult.
What you can do is lag proxy whatever the main branch is to catch it in time, or just keep revisions of your mirror that you script and tag yourself. It’s like a daily backup you can go back and look into.
It’s going to waste a ton of space and time, but it would effectively create a stop-loss on someone nuking history, which generally is just not a thing that people do because it’s entirely stupid.
I mean…it makes sense in some ways, but absolutely fails in others. This will be problematic to start for sure.
Compose is just a single binary. There is no wrong way to install it really as long as it can find all the needed shared libraries and such.
If in doubt, look at the manual install instructions. Run through that, and see if it behaves any differently.
Some logs from the startup of a this container would help. Just run
docker compose up(without the -d) and you’ll get all the output up front.