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.
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 think it's pretty doable, but there are some things you should think about:
For my domains, I'm running
nsd
in two different VPSes, and the way that I edit my zones is that I have a script that converts a shorthand format (that I came up with) to a standard zone file and thenrsync
s (using hostnames declared in my .ssh/config files) the zone files andnsd
configuration files to both servers. The script then reloadsnsd
.I chose
nsd
because it felt like the simpler option, no troubles so far. I use them directly on my debian hosts, no containers.I have no monitoring, but I should. My terrible excuse is that the infrastructure I'm running is not critical and it's on the same hosts as my nameservers, so they usually go down together. I wouldn't put client domain names in there without monitoring.