If the other services are exposed on local ports, you can have NPM forward to those.

For anyone confused by “Nextcloud” in the title, it’s just the blog attribution—Nextcloud isn’t involved in the acquisition.

As a casual self-hoster for twenty years, I ran into a consistent pattern: I would install things to try them out and they’d work great at first; but after installing/uninstalling other services, updating libraries, etc, the conflicts would accumulate until I’d eventually give up and re-install the whole system from scratch. And by then I’d have lost track of how I installed things the first time, and have to reconfigure everything by trial and error.

Docker has eliminated that cycle—and once you learn the basics of Docker, most software is easier to install as a container than it is on a bare system. And Docker makes it more consistent to keep track of which ports, local directories, and other local resources each service is using, and of what steps are needed to install or reinstall.

DIdn’t Intel stop making NUCs?

Was it RAID 0 (striped), or RAID 1 (mirrored)?

In general, a mirrored RAID is best for minimizing data loss and downtime due to drive failure, while separate volumes and periodic backups is best for recovering from accidental file deletion or malware. (I.e., if a RAID gets told to write bad data, it’ll overwrite the good data on both drives at once.)

If you want the best of both worlds with just two drives, try zfs—you can mirror the drives to protect against drive failure, and make snapshots to protect against accidental data loss. (This still won’t protect against everything—for that you should have some kind of off-site backup as well.)

I’ve been running two NC instances for over five years (linuxserver docker images)—one has been issue-free, and the other had sporadic issues like OP is describing… but not for the last year or so, so I assumed the issue had been fixed in an update. Or maybe the problem was the network configuration instead of NC.

It’s a set of plugins for standard MediaWiki. (It was originally intended to be part of Wikipedia, but there were performance issues on that scale. It’s used by many smaller organizations, though.)

It may be overkill for most—it’s not the easiest thing to set up and it’s got a high learning curve—but for heavy research and world-building I’ve found Semantic MediaWiki revolutionary.

You can create auto-generated and auto-updating maps, timelines, tables, etc., and make live queries that pull information from all relevant pages. (For instance, if you write pages for a bunch of events and annotate them with dates, locations, and which characters are involved, you can create a map and itinerary for each character and a list of all the characters they’ve met or interacted with. If two characters meet in a particular place, you can generate a list of the most recent events that happened to each character, recent events at that location, past events where both characters were present, people and places they know in common, etc. And if you decide to shuffle events around, everything updates accordingly.) It’s also great for collaborative writing, it can be accessed through the web from any device, and it has automatic versioning. It’s almost insanely powerful, and of course it’s FOSS.