

Going to try to convert two 2-post racks into a 4-post rack today. Dreading the mess though.


Going to try to convert two 2-post racks into a 4-post rack today. Dreading the mess though.
Not sure if it’s actually feasible today, but in the future when all the Internet routing and consumer devices are compliant, something something ipv6 has enough address space for every device many times over to have a unique address. I’m guessing there’s still too many links in the chain that won’t be setup for ipv6 to work, but it’s worth your research.
Probably more realistic to work out the complication you’re concerned about with reverse proxy and a VPS + VPN.
Ah, wasn’t aware of that, makes more sense now. Seems like OP needs to pipe everything through someone else’s server, or fork over for the static IP, until IPv6 is finally universally functioning. I’ve seen good things about Cloudflare, at least as long as they aren’t doing multimedia.
Just use a dynamic dns service and expose the stuff you need to access publicly, publicly. If you want to be extra careful, or secure services that otherwise have no security, your reverse proxy should be able to forward auth, which forces people to login before the request is handled. This gives you a single point of security failure again, which I’m not seeing as any different from whatever you’re thinking about with wireguard and a vps. You can also selectively configure which services use forward auth, which are fully public, and which aren’t accessible outside of LAN addresses. This would give you the option to use something like Tailscale for your private stuff when away from home without having to use the forward auth.


Regardless of what the remote access test says about it being available, I had to manually port forward to fix this same issue.
Dokuwiki user here. Your cons are true, but compared to the cons of other ones, they are all solvable. The concern with a plug-in being required to do something is silly. It’s open source and the plugin system is limitless. If it’s ugly, make a theme. I’ve never had a problem with article titles being mutilated, but then again, I treat the file name (e.g. the url of the page) separate from the root header as you’re supposed to.
Considering your comment about search being awful in another wiki, it’s pretty good in Dokuwiki.
Considering how much you care about plain text, you should probably discount the con about file names as I’m pretty sure that’s part of why Dokuwiki does what it does. It’s an actual text file sitting in a directory that matches the path.
For what it’s worth, I admire Obsidian. If it’s a personal project with no intent to share, that’s what I’d use. For business or public hosting, I’d use (and do use, at my company) Dokuwiki.