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
As a side note, don't be cute and pick port 221 or 2222 or 22022 or whatever that's got "22" in it.
I know that sounds silly but the slightly less stupid bots are written by people who understand people do things like that and account for them, and thus port 2222 isn't actually better than 22, or whatever.
imho - never expose that shit anyways, and VPN into your local network first. Only thing I ever expose to the internet is 80/443.
At the very least, if you're going to expose an SSH session to the internet, set up some sort of port-knocking. It's security by obscurity, sure - but it will keep all but the most ardent intruders out.
Agreed, but sometimes you have to expose things you'd rather not; I just figured I'd mention that almost everyone's immediate urge to just go 'port 2222! that'll do it!' isn't exactly better than doing nothing anymore.