What does HackerNews think of cloudflared?
Cloudflare Tunnel client (formerly Argo Tunnel)
https://www.cloudflare.com/products/tunnel/
https://github.com/cloudflare/cloudflared
https://developers.cloudflare.com/cloudflare-one/connections...
Edit: If anyone is interested in self-hosting, it's stupid simple with cloudflared. I have a 2017 Google Pixelbook running Ubuntu on custom firmware that's serving a Flask-based website. It sits on my desk charging while connected to a guest wifi network. It receives a 100/100 Mobile PageSpeed score and takes 0.8 seconds to fully load.
It works with all NATs/CGNATs by connecting from the pi over a bidirectional WS connection. PI <-> WS <-> Cloudflare. SSL is done on the cloud, not on the pi.
Install any web server on the pi and "cloudflared" to proxy it.
https://developers.cloudflare.com/cloudflare-one/connections...
As someone who's trying to get to grips with the Linux filesystem conventions, would you mind elaborating on a) why that's wrong, and b) what you would suggest instead? This reference[0] suggests that `/usr/sbin` is for "general system-wide binaries with superuser (root) privileges required" (and `/usr/bin` for those that don't require root privileges). I've therefore been using them in my homelab for binaries like the Cloudflare Tunnel Client[1]. Where instead should I have installed it?
* If to a "well-known location" that is commonly-used by convention, how should I find out what that is?
* If to a custom location of my choosing, how should I communicate its location to scripts/tools that _use_ that binary? I see later in your comment that you suggest "Add whatever folder to the user's PATH environment variable to make it easy to run.", but that doesn't seem like a scalable solution for a multi-user environment?
That being said, I love that someone is working on making this stuff easier to do, it was finicky to get it setup myself. I would be backing it if I hadn't just done it already.
I wish Kubesail all the best and I hope they succeed.
- Tunnel (cloudflared): https://github.com/cloudflare/cloudflared
- Argo as ingress (k8s): https://github.com/cloudflare/cloudflare-ingress-controller/
The documentation is not great / accurate but with a bit of fiddling I have it running as a systemd service (launchctl on MacOS). I'm using the /metrics endpoint to get details in Prometheus on the stats.