view the rest of the comments
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!
Are you confusing "ports" with "interfaces"? I can see that happening since we do colloquially refer to both as ports depending on context.
Each service will bind to it's own "port" which is tied up by that service. However each interface (the external physical connection) supports like 65,000 software ports.
So in practice, no, you don't usually need more than one physical network connection to run multiple services.
I didn't know that you could have two "interfaces" vs "ports". I was talking about the physical ports knowing this. This helps me understand what @fiivemacs means. I'm definitely not going to be using more than one provider. Thank you!