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'm just barely okay at self hosting applications, so using Unbound together with Pi-hole poses a great challenge. Technitum DNS is a whole package and the GUI is user-friendly to me. But, after using Netbird on VPS (for the reverse proxy mostly), because of a different sub-domain being used, I think I don't need Technitium anymore though it continues to work so I have no reason to change.
Pihole + unbound on the same box as my DNS has been super simple for me. I didnt do a lot of extra configuration for Unbound, I used mostly the guide that was on Pihole official documentation.
As for reverse proxy, I have Caddy setup. And to access my homelab I use wireguard.
Most of my services run on a separate box running docker.
I've woven most of it together bit by bit. I'm slowly upgrading different pieces and its lead me down a rabbit hole. So I found this post intriguing.
Biggest hurdle with Technitium for me is the lack of documentation. I can say the compose file they provided has lots of comments. That doesn't solve for a few pieces for me though. Systemd-resolv uses port 53 on my host box, and I have to find out the ramifications for disabling that and using Technitium. That and I am unsure of what extra capabilities I have to grant that container. And I have to find out how adding it to my reverse proxy docker network.
So its gonna be trial and error I suppose! I'm looking forward to getting DoT or DoH or DoQ setup.
I couldn't agree more about the lack of documentation for Technitium. Thank God it has an interface instead of command line only. Don't know anything DoT or whatever. Guess I'm not using Technitium to it's full potential. That said, I appreciate it being a total package of DNS server and adblocker.