viewtube VS traefik

As for my iPhone I now use viewtube.io (you can also self host it if you want) and I am very happy of the result.

Self-host Viewtube and silently redirect all Youtube traffic to it. 😁

After using invidious, then piped, I settled on ViewTube. https://github.com/ViewTube/viewtube-vue better UI than invidious, not as obnoxious as piped.

I run ViewTube having gone through 3 other front ends, and although not perfect, it's the best I've found for my needs. But like you say, the problem I have is I really do not give a flying funk about youtube, and wish there was a way to transparently proxy all youtube requests to viewtube. Short of as you say doing a local DNS entry for youtube and knocking up some kind of certificate, I'm stumped. I have to rely on per-client solutions like UntrackMe or PrivacyRedirect.

Slight aside: try out ViewTube as well. I was running Piped for a few months until yesterday when I found this. I found Piped needlessly complicated, but better than raw invidious. Viewtube for me is the best of both. Still not perfect, but I'm trying to set up a dev environment to contribute if I can atm.

Hi can viewtube be put into the Video Streaming section. https://viewtube.io, https://dev.viewtube.io

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

Not as good though. Case in point: https://github.com/traefik/traefik/issues/5472#issuecomment-... (that's just from this morning)

I'm speak objectively here. Of course, any built-in auto HTTPS that works (more or less) is better than none. Traefik uses an ACME library that was originally written for Caddy. After the original author left that project, Traefik team started maintaining it. Caddy's users' requirements exceeded what the library was capable of, but unfortunately there was friction in getting it to achieve our requirements. So I ended up writing a new ACME client library in Go and, together with upgrades in CertMagic (Caddy's auto-TLS lib), Caddy has the more flexible, robust, and capable auto-HTTPS functionality.

That is to say, not all auto-HTTPS functionalities are the same.

We'll use Traefik, an open source cloud native gateway that can plug into a Kubernetes cluster. It has the concept of "middleware" that can process API requests before passing them through to a backend. We can configuring a rate limit for all of our API endpoints by matching on the request path:

I did the same question here and here

Sadly there is currently no way of doing so. https://github.com/traefik/traefik/issues/6999

Traefik is another widely used system that has automatic configuration and offers support for more things like swarm/kubernetes/etc.

I have a webapp which I currently have deployed by running nginx in a container. Works as it should, however I am intersted in adding more observability to the webapp and found this reverse-proxy https://github.com/traefik/traefik which seems to expose some nice metrics which can be useful for observability.