Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I migrated from pihole to technitium a few weeks ago and it was so smooth.
Native support for clustering is huge. I didn't even realize how complex managing the pihole had gotten trying to get it to sync to multiple instances.
Not very complex. Use nebula-sync in docker.
I was doing basically this with a different sync tool, but I had a couple issues with it:
I've been a very happy Pihole user for years and years and Pihole 6 is the best yet, but once you're dealing with multiple pihole instances, Nebula Sync and Unbound, then Technitium is actually simpler to manage since it does all that natively.
That's good to hear!
One feature I wish I could find was automatic DNS record creation for new docker containers I spawn.
Can't wait to check out Technitium.
Oh do I have a treat for you, check out DNSWeaver.
It's designed to do exactly that, to automate creation of DNS records for container services. I use it with Traefik. It reads from the same labels that Traefik already uses to proxy services but if you already use another reverse proxy and don't want to switch it supports dnsweaver-specific labels as well which are easy to add to your current deploys.
I used it both with pihole and technitium and actually used it to make the migration easier. Great tool.
Good news is that I was playing around with DNSWeaver, and got it working with Pihole. However, this gives me incentive to move off from Pihole because DNSWeaver can't create TXT records for tracking which DNS records it creates so that it can clean up after itself.
So now I am torn between Adguard Home and Technitium. I just wish I could find a guide for getting Technitium working to at least on par with what I have setup.
I deployed Technitium with docker, but generally this got me heading in the right direction with the initial setup. It's more of an overview and quickstart than an in depth guide though.
Thank you! A start was what I was looking for!
Oh my. I am so thankful you shared this! I will be reading up on this and testing it out likely.
Currently I use Caddy. Which I eventually would like to automate Caddy with this: https://github.com/lucaslorentz/caddy-docker-proxy
Currently I build my own Caddy based off the official image with the cloudflare plugin
DNSWeaver has support for caddy labels too! Specifically for use with caddy-docker-proxy. So yeah, really good fit for your architecture.
Again, thank you for your suggestions! I am contemplating switching to Adguard or Technitium from pihole. Just gotta figure out how I am gonna approach it