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
Your not wrong. I guess that's why I'm posting here, just trying to figure how what I'm doing and what it all means
If you have any advice for learning I'll definently look at it
Hmm, I would propose setting things up in your LAN step by step. But it would take a long time.
It's something someone experienced could make (poc style - proof of concept) in an hour or so, just to show how it works, but it's a lot for a beginner.
Still, you could start making a simple Webserver hosting a page and then setting up dns for it and pointing a client to the dna server and see how that works.
It's infinetly expandable.