server.coop VS traefik

An update: I have found someone for the room in the current house, but that location is very temporary, as it is not conducive to the kind of development I am looking for. What is consuming all my time, and is the reason I have not been actively working on further organizing, is that I am instead working on a prototype for a commercial version of Roomba that automatically plugs itself into a standard power outlet. When I get the very basic prototype of the idea done, I will write up a business plan that details my thoughts on the further steps towards commercialization and post them widely for feedback and additions. As the current location for these ideas is only in my head, I need to get them out in physical form before I can seek collaboration on this endeavor. Hopefully this will be done in a month or two. However, if other people have product ideas that are further fleshed out or are interested in taking over another idea I had that is currently on hold due to lack of interest and time (a cooperative cloud provider https://github.com/TheOtherRealm/server.coop that needs a complete overhaul, or more likely to start from scratch, that replaces the Docker swarm with something better), by all means share!

Pronounced "traffic", Traefik is a modern HTTP reverse proxy and load balancer aimed at making deploying microservices easier. It integrates with your existing infrastructure components such as Docker, Kubernetes, and others, and configures itself automatically and dynamically. The latest version adds lots of new options and enhancements such as adding healthcheck options, support for custom headers, and more. Read the migration guide on how to update to the latest version which is now required due to breaking changes.

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.