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'll have to disagree with you there. SSH is super well maintained and understood, and massively useful for the risk you do run. Who knows what's going on with all the random projects people are hosting. I'd rather have SSH exposed than almost anything else.
What would you do to provide access to some less tech savvy friends. I'm thinking of dropping a SBC with wireguard and a proxy onto a friend's network, that way everything is under my control, and I can lock down the wireguard connection however I want, but I haven't gone down that route yet.
I was thinking more along the lines of simply thowing up a port to SSH into. No Fail2Ban and no keys, just a password.
I would just containerize and reverse proxy, but I understand the hesitation, wireguard would be preferable.