105

Selfhost wiki (personal) (wiki.gardiol.org)

submitted 3 months ago* (last edited 3 months ago) by Shimitar@feddit.it to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

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.

top 29 comments

sorted by: hot top controversial new old

[-] N0x0n@lemmy.ml 24 points 3 months ago* (last edited 3 months ago)

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-domain

There are actually wildcard SAN certificates where you can access all your subdomains with a single certificate: https://*.mydomain.com

Or you can add all your subdomains in a single certificate.

Great work and thanks for sharing !

[-] TheHobbyist@lemmy.zip 5 points 3 months ago

You are right and I would add that this is even a privacy and security measure, to make use of wildcard certificates. The reason is, those subdomains will be public because of websites like crt.sh which show all subdomains which have their dedicated certificate. Obfuscation can be helpful in not disclosing which are some services or naming schemes you use for yourself even if it is only meant to be for internal use.

[-] vegetaaaaaaa@lemmy.world 1 points 3 months ago

Obfuscation can be helpful in not disclosing which are some services or naming schemes

The "obfuscation" benefits of wildcard certificates are very limited (public DNS records can still easily be found with tools such as sublist3r), and they're definitely a security liability (get the private key of the cert stolen from a single server -> TLS potentially compromised on all your servers using the wildcard cert)

[-] Shimitar@feddit.it 4 points 3 months ago

Yes, you are right, I have updated the information.

[-] TheHolm@aussie.zone 3 points 3 months ago

using wildcards is really bad security practice. and at age of ACME absolutely unnecessary.

[-] TheHobbyist@lemmy.zip 2 points 3 months ago

Can you elaborate on why it is a bad security practice? It's the first time I'm reading about it and I'd like to read more about it. Thanks!

[-] Shimitar@feddit.it 4 points 3 months ago

One of the risks associated with wildcard SSL certificates is the increased attack surface they introduce. If one subdomain becomes compromised, it opens the door for potential attackers to gain unauthorized access to all subdomains secured under the wildcard certificate. (first google link)

[-] cron@feddit.de 1 points 3 months ago

While this argument is valid for a larger domain, it doesn't really matter for the small selfhoster.

[-] Shimitar@feddit.it 2 points 3 months ago

Using let's encrypt certbot is so easy and automated that I never bothered for wildcards anyway, so.

[-] lorentz@feddit.it 2 points 3 months ago

The advantage of wildcard certificates is that you don't have to expose each single subdomain over internet. Which is great if you want to have https on local only subdomains.

[-] TheHolm@aussie.zone 1 points 2 months ago

If you still use HTTP for cert verification on ACME, you are doing it wrong. Use DNS-01 only, there is no need to allow any inbound traffic to your servers. and HTTP will not give you wildcard anyway.

[-] lorentz@feddit.it 2 points 2 months ago

Yes, you are right, I already use DNS validation. But it is just it is easier to request a single wildcard certificate for my domain and have all the subdomains that I use for the local services defined only in my local DNS. I cannot fully automate the certificate renewal because namecheap requires to allowlist the IP that can call its API, and my ip is dynamic. So renewing a single certificate saves me time. Also, the wildcard certificate is installed on a single machine, so it is not the I increase a lot the attack surface by not having different certificates for each virtual host.

[-] N0x0n@lemmy.ml 2 points 3 months ago* (last edited 3 months ago)

That's true. But it doesn't take away the possibility to use them in a selfhosted environnement.

Large enteprises like facebook and google still use them, but they have the backing to secure them safely.

Also, there is always the possibilty to add all subdomains in one certificate which takes away the wildcard subdomains.

[-] Shimitar@feddit.it 1 points 3 months ago

Fully agree

[-] Brunette6256@sh.itjust.works 6 points 3 months ago

Is there a section about the wiki on the wiki? I was wondering what the wiki tool is.

[-] wolre@lemmy.world 6 points 3 months ago

It's dokuwiki.

[-] Shimitar@feddit.it 1 points 3 months ago

As already stated, it's Dokuwiki. I tried a few and this was the best compromise between features and complexity for my needs.

[-] crony@lemmy.cronyakatsuki.xyz 5 points 3 months ago

I recently started something similar using bookstack as the software behind.

Still severely lacking in content but am willing for anyone who has time and something interesting to write in it as long it's connected to tech, preferably linuc and open source software.

Here is the link and if anyone want's to contribhte I'm more than willing to accept a couple editor to grow the content on it.

https://wiki.cronyakatsuki.xyz

[-] Shimitar@feddit.it 3 points 3 months ago* (last edited 3 months ago)

Now the big question is: are you an Arch or a Gentoo lover? Just joking.

Good job! Keep it up

[-] crony@lemmy.cronyakatsuki.xyz 2 points 3 months ago* (last edited 3 months ago)

At one point was arch lover, then I became a gentoo lover.

Now I'm on nixos because gentoo didn't have a good retroarch package.

[-] Decronym@lemmy.decronym.xyz 4 points 3 months ago* (last edited 2 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
DNS	Domain Name Service/System
HTTP	Hypertext Transfer Protocol, the Web
HTTPS	HTTP over SSL
IP	Internet Protocol
SAN	Storage Area Network
SSL	Secure Sockets Layer, for transparent encryption
TLS	Transport Layer Security, supersedes SSL
nginx	Popular HTTP server

8 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.

[Thread #556 for this sub, first seen 29th Feb 2024, 10:35] [FAQ] [Full list] [Contact] [Source code]

[-] superbirra@lemmy.world 1 points 3 months ago

nginx isn't an acronym lol bad bot

[-] schmorpel@slrpnk.net 4 points 3 months ago

Thanks a lot for sharing this. I'll keep it bookmarked for later reference, looks very cool!

[-] owen@lemmy.ca 3 points 3 months ago

Quite useful... Thanks for sharing

[-] psy32nd@lemmy.world 3 points 3 months ago

Good work. Added to favorites.

[-] Fisch@lemmy.ml 1 points 3 months ago

Might be worth adding a section for web UIs that make managing certain things easier. For example, Cockpit or Nginx Proxy Manager.

[-] Shimitar@feddit.it 4 points 3 months ago* (last edited 3 months ago)

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.

[-] AFLYINTOASTER@lemmy.world 1 points 3 months ago

What lead you to believe NPM is useless/messy?

[-] Shimitar@feddit.it 2 points 3 months ago

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.

this post was submitted on 29 Feb 2024

105 points (97.3% liked)

Selfhosted

37196 readers

231 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz