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
You can already do that without a reverse proxy.
A reverse proxy allows you to have multiple services running on 0.0.0.0:XXXA
For example you might have two websites at a server on 192.168.0.123
Your server will be setup to show those websites at two different ports, say "192.168.0.123:123" and "192.168.0.123:321" - with foo.com on 123 and example.net at 321
Your reverse proxy will listen to requests on port 80 (where websites are usually served) and look at each request. If it's a request for the website at foo.com, it'll send it to port 123. If it's a request for example.net it will send it to port 321
But the client who is requesting the sites will only see port 80, at the same IP address for both sites.