I remember Gitlab requiring quite a large amount of resources, so if you’re talking about a solo project, I’d skip it and go with something a lot leaner like Gitea, personally.

I’ve never had any security issues with GitHub in the past though, and extended features are free for open source projects, so it’s kind of hard to ignore.

If it didn’t give you problems, go for it. I’ve run it for years and never had issues either.

Keep using the NAS as long as it keeps being useful. Just for moving some services off onto something else, it sounds like you could just get a low power minipc of some sort and run your services there. An N100 or AMD APU would work just fine for Plex (transcoding on Intel may be a bit better).

If you’d rather go the extra mile and build a larger machine with a disk array, you don’t need anything super wild for the CPU or memory based on the services you’ve listed.

Home Assistant for family members

This

It’s sad we’ve come to this because nobody can afford an actual home.

👍

You’re asking for a lot of different things that don’t align, so instead of trying to guess what you need, let me just throw a few things out there:

• if you want transcoding that isn’t constantly tied to GPU, you want an AMD chip of some sort. If you’re trying to be efficient, an APU model.
• you probably want to just merge all your data into a single disk array. Running multiple on one system is pointless and inefficient.
• separate your CPU needs from storage. Like you said, maybe you just need an ultra low power NAS, and then different machine to handle compute.
• skip SSD for any network storage. Yes it’s more power efficient, but if you’re talking bulk storage, you’re wasting resources for smaller volumes where it won’t matter if transferred over the network. SSD is good for local-only for the most part.

The issue is more likely to be your port selection and UDP being discarded on networks with captive portals that generally only allow certain ports and traffic. Try using some other common UDP service ports like 53/DNS if not already in use, or maybe 5060/SIP, or even other common VPN ports.

Unless they’re running L7 hardware in the hotels, I doubt they’re doing any kind of packet inspection.

It’s more important to get that dmesg output AFTER an event happens, but before a reboot. What you’re running doesn’t matter much unless you have live metrics of their behavior or resources.

There isn’t one.

Stick to the best brands out there that have been benchmarked.

Need logs to be able to tell you much. Get some output from dmesg after it happens, but before a reboot. Syslogs couldn’t hurt. Maybe setting up a metrics exporter to another machine could give you a peek into what is happening with resources.

Also give some details about OS and what you’re running on it.

Didn’t realize we all were now incapable of looking out the window. That seems like something an absolutely incapable person would do because they’re way too lazy.

IPFS is like a dead Multiplayer game, or an Onion network. Check it out.

Lol. You checked on IPFS lately? Different times. Different world.

Tell me what I’m misunderstanding here.

*but relies on IPFS.

Useless.

EFI bootloader won’t have this problem. Adjust accordingly, and things will be fine.

I very much did. Read up.

Because IRC doesn’t “work fine”.

It’s a 50-year old solution to no modern problems where everything about it has been solved in better ways.