I have finally got my selfhost wiki up to a satisfying shape. Its here: https://wiki.gardiol.org
Take a look i hope it can help somebody.
I am open to any suggestions about it.
Note: the most original part is the one about multi-homed routing and failbacks and advanced routing.
You must log in or # to comment.
Thanks for sharing, very cool stuff in there and great job ! Bookmarked !
While reading through your reverse proxy concept post, I think this statement is wrong:
As a sub-domain: - Cons: require additional certificates for HTTPS/SSL for each sub-domainThere are actually wildcard SAN certificates where you can access all your subdomains with a single certificate:
https://*.mydomain.comOr you can add all your subdomains in a single certificate.
Great work and thanks for sharing !
Yes, you are right, I have updated the information.
Is there a section about the wiki on the wiki? I was wondering what the wiki tool is.
It’s dokuwiki.
As already stated, it’s Dokuwiki. I tried a few and this was the best compromise between features and complexity for my needs.
Thanks a lot for sharing this. I’ll keep it bookmarked for later reference, looks very cool!
Quite useful… Thanks for sharing
Good work. Added to favorites.
Might be worth adding a section for web UIs that make managing certain things easier. For example, Cockpit or Nginx Proxy Manager.
I think NPM is useless (in my use-case…) and can get things more messy, but I plan to check on cockpit later on indeed.
NPM isn’t bad in itself, but NGINX configuration is basically static and IMHO don’t require a dedicated GUI.
What lead you to believe NPM is useless/messy?
Yeah, i kind of wrote badly. I mean NGINX configuration is simple enough and static enough not to need a dedicated service for my use case. I don’t feel the need to mess with NPM. I have a neat folder structure under nginx config so that adding one service is pretty clean and simple and editing one too.
