So, mentioning you like this shows up in the guestbook? @fabio@manganiello.blog

Looks pretty cool!

Still waiting for my success. Pihole randomly doesn’t answer DNS requests in time, causing a lot of trouble between my services. It’s happening since I switched to dnsmasq in opnsense (which is upstream for my local domain for Pihole), but also for external domains. Can’t nail it down and am this short of reconsidering my whole network setup. It used to work fine for over a year though…

Opnsense dnsmasq is DHCP for my servers and also resolves them as local hosts. (e.g. server1.local.domain) and Pihole conditionally forwards there. Since the issue is also when resolving external domains, it shouldn’t be related, but the timing is suspicious. I also switched the general upstream DNS.

Pihole does have some logs indicating too many concurrent requests, but those are not always correlating with the timeouts.

I know it’s DNS, I just don’t know where yet.

Thanks for the example! The reasons you mentioned were why I wasn’t looking into it more (using it for my local docs as well).

As someone from Northern Germany, I’m obliged to check out MoinMoin!

Thanks, I missed that.

How did you approach finding the proper plugins?

Yeah it seems like it’s doing too much for me.

I installed that editor, but that’s the point, I’m looking for something where I didn’t have to puzzle too many extensions together.

I’ll probably give DokuWiki another try. Bookstack is not what I’m looking for, but maybe I’ll have a look at wiki.js!

Great reason! On first glance it seems to be a bit too minimalist I think.

I used to host DokuWiki at some point but I inherited it and never really got into it. Maybe I should give it another try. It was also a native install and I found the updating mechanism to be annoying, but that should be solved with containers.

I’m using Bookstack as well to document my private stuff but it’s not what I’m looking for.

And with production run I mean produced at the same charge or the like. As those have a higher chance of failure. If you buy two new from the same shop, odds are that they came in the same shipment etc.

The downside is they are more expensive, the louder part is for big servers I think, but not HDDs

And yes, I was talking about used ones, sometimes they’ve got the SMART values listed, sometimes I ask

I’d go for the second option. Just make sure they are not from the same production run with similar history (operating hours) as it would increase the chance of both failing at the same time.

You can also check eBay for enterprise HDDs with 90+ remaining SMART values. They are far cheaper than new and usually fine.

They’re right here in the shelf :-)

They don’t log, at least not to my knowledge, they aren’t part of the OS.

They are behind an opnsense, but the broken one is not reachable from inside the network as well and the other one is reachable from outside perfectly fine

I’m on calibre web automated but I’m looking to migrate away. Gets tons of features that I’m not using and I can’t keep up with. Also the slop release notes are barely readable. I put up an issue for that, not sure if it’s gonna help.

I just add a book via the web interface now and then and later download it via OPDS. Probably giving Booklore a try.

That likely means the server is still up and just the Lemmy containers/just the frontend container is down. The default setup has nginx proxying the /pictrs to pictrs I think.

Copying my other comment. It opens PRs to change the tag from the docker image.

I have all my compose stacks in git. They’re deployed from their git repos with Komodo.

Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.

There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

I have all my compose stacks in git. They’re deployed from their git repos with Komodo.

Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.

There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo