tailscale is a vpn. you don’t need cloudflare for it. you do need to set up the tail scale container with your credentials from tail scale, which they have guides for. after that, log in on your machine and click the connect toggle and you’re in.
the exit node is if you want to look like you’re at your host computer.
5 square kilometers. dayum. (I think that’s big. it sounds big.)
During the tests, the 5,000 square-metre kite - about the size of 11 standard NBA basketball courts
Finally, we’re not using American football fields
what an experience! thank you for sharing :)
that was a fun read and I appreciate the guy’s sarcasm in all of it. I can only imagine what that meeting with Gates was like.
I made an edit to the blog. It looks like that approach didn’t work.
Summary for those who want the tl;dr - I found a github issue where someone “solved” it by blocking network access to longhorn outside of the backup hours. I am now trying that approach with cron jobs to set and remove an egress policy to block access.
Hopefully this will solve it.
I’ll include mine to show that it’s not unusual to support them! it’s my favorite and most used self hosted project
the complaints in these comments is an illustration of why the left doesn’t accomplish jack squat
that’s quite a long compose file.
the way that I use cloud flare is with tunnels since my ISP blocks my ports. I have cloudflared running that connects to the cloudflare tunnel, which has a map of domain name to a service name, which is how services are accessed externally.
tailscale connects to tail scales main service and that’s how I access internal systems. at least that’s how I’m running it.