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
I did something similar in my homelab using frp and traefik. Traefik picks up configuration in its normal way and handles all inbound traffic, doing SSL termination locally even. frpc (client) sits next to Traefik, dials out to my frps (server) machines, and passes incoming connections to Traefik via the proxy protocol. I point my DNS at the frps machines in the cloud and they are configured to let the clients connect to them and take over basically any port they want.
I think there are ways to get frp to do basically exactly what you want, but I use it for a slightly different case.