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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
Some of the things in my house were set up so long ago, and running so smoothly, i havent looked at them in years (other than auto updates) now i'm afraid i've accidentally left some security hole without realizing it
For example, i set up cerbot 10 years ago and back then there was no DNS challenge, so i had to open my webserver to port 80 to renew.... well since everything was running from https/443, i decided to block port 80
so i edited the systemctl unit for certbot to temporarily open port 80 for the renewal, and close it right after...
It was only 5 years later i realized i made a mistake and port 80 had been open for 5 years to the open internet
Probably no harm since its a public server anyway... defense in depth is the key