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 use a reverse proxy (caddy), and point a domain at my machine.ts-domain.ts.net which hosts caddy
this way I can go to service.my.domain instead of machine:port as long as I’m connected to tailscale. any devices not on my tailscale network just get bounced if they hit the domain
You have a CNAME record that points service.my.domain to machine-that-hosts-caddy.ts-domain.ts.net, and with tailscale enable it hits the caddy server and then reverse proxies it to the machine:port of "service"? Which may or may not be the tailscale IP address and port?
Basically yeah.
CNAME points my.domain to *.machine-that-hosts-caddy.my-ts-domain.ts.net
caddy running on that machine directs subdomains to machine:port pairs, where “machine” is either the tailscale name or IP for the machine hosting the service
Thanks!