No, not self-hosted. That's why I put the caveat in here. I am a self-hoster, but this is beyond that scope, but I still want that vibe / workflow where possible.
Randos will not edit. There may be users who edit in the future, but it's not a "register and edit" sort of thing. It's more of a living breathing guide, that has the flow of Wikipedia (as well as the SEO benefits--it's the type of information people will search and want to find, and land on it in this format to learn and reference).
Really it's better to think of it as SEO-optimized wiki formatting. There may be editors in the future, but not in the near future, as a lot of the content will be covered. If there's editing, it'll be submission-based and approved or denied.
Holy shit man. I am sorry for your pain. It’s definitely not your fault and insane that you could conceivably be put in a position to do that—and I’m sure no one would let that happen to you today in med school. Not your fault for the patient condition nor the condition that set you up to administer unsafe care.
What is the software setup when you're actually configuring the minipc/box? Beyond the hardware architecture of the local network, what is the actual stack I should be pursuing and how is it implemented?
For example: I read lots of great things about OPNsense, Wireguard, DietPi... but I don't know what the exact stew should be and how to set it up ELI5 style.
I was lazy in my langauge. I meant DOCSIS modem -> router/firewall with everything -> access points or hardlined ethernet recipients. Current setup is Arris dedicated (non-wifi) 3.1 to Linksys mesh.
99% of demands are local network performance. No mega streaming needs or huge external traffic. Upload on wireguard (Jellyfin or otherwise) will be pretty limited to a single user at once. But this is not critical. Local network is my usecase.
I am 500/50, will probably up to fiber as soon as it's available. But again not a lot of external traffic, hyper limited.
So get a switch between the router/minipc/whatever and the rest of the local network instead of many on-board ethernet?
How do you get around RAM requirements on SBC home servers with little devices like this? I am often streaming 4K files and the encoding/decoding can sometimes be mildly intensive depending on the file.
No, not self-hosted. That's why I put the caveat in here. I am a self-hoster, but this is beyond that scope, but I still want that vibe / workflow where possible.