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!
@jaackf
SyncThing. It's the best sort of selfhosted program. You set it up once and then never think about it because it just keeps quietly doing what you wanted.
Wikis can be great if you've got a few folks that need to coordinate information.
An RSS reader/aggregator.
An RSS reader (I use Miniflux), ended up being extremely useful
Actual Budget I use to track my finance.
Duplicacy for backups to OneDrive and Backblaze
Photoprism as Google replacement
Parties.
DNS. It's always DNS
for better or worse it is, (though I don't recommend newcomers to boot up a bind server to manage their dns, pihole is probally the best starting point)
Indeed, dnsmasq would be much easier to handle than BIND OOTB. I have personally not come across a reason to use BIND for myself, and struggle to see its appeal out of the enterprise/enterprise-like labs, but I don't really know much about homelabbing either
In my (our) case we use bind to run an authoritative resolver for our domain (I am sysadmin for a uni computer society, we have our own (physical) servers)