docker-ripper VS traefik

I haven't tried this but it looks like a very good option if you need to do a lot of discs https://github.com/rix1337/docker-ripper

So I was able to mess around with it for a bit last night. Aside from attaching it to a VM, which worked as expected, the only thing I was able to do with it was this https://github.com/rix1337/docker-ripper

https://github.com/automatic-ripping-machine/automatic-ripping-machine or https://github.com/rix1337/docker-ripper

Do you use docker? You could use the ripper container and use handbrake container. You’d set the output directory of ripper to be the handbrake input directory. Just put the disk in the drive you have setup and ripper will do it’s thing. After it’s done handbrake will detect a movie and encode it using your settings.

Ripper: Automatic Blu-ray ripping

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.