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
Create the subdomains and have them all point to your PUBLIC IP (10.172.. But keep in mind 10... Are -not- public ip)
You will need to setup redirect from your router/gateway to your internal ip.
Unless you are on cg-nat (that would explain a 10... class ip) in that case, you will definitely need a real public static ip
To "match" the various ports all to 443, you will need a reverse proxy, since those ports are not standard. This could be mitigated with srv DNS records, but I really strongly suggest not to go public without https and reverse proxy.
SRV records won't help with browser traffic.
My real ip starts with 89. The 10.172.172.172 was just an example.
Bad example, you picked a reserved range that confused me :)