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
Opening ports essentially allows other computers on the internet to initiate a connection with yours.
It's only dangerous if a service running on those ports can be exploited.
"If" is not the correct word choice. It's only dangerous when a service on the port gets exploited.
Driving a car is only dangerous when you die in a traffic accident.
your logic doesn't check out.
If it's exposed to the internet it's a matter of when, not if, it is compromised.
to reduce attack-surface, if there's no reason for the port to be open, don't open it.
This, coupled with the fact that firewalls are protocol-agnostic. You can, for instance, use 'port https' in your Packet Filter config instead of 'port 443', but that simply means that PF will block/pass traffic to whatever service is bound to that particular port, and NOT https connections in general.