caddy-ratelimit
ingress
caddy-ratelimit | ingress | |
---|---|---|
4 | 7 | |
183 | 574 | |
- | 2.3% | |
6.4 | 8.3 | |
7 days ago | 1 day ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
caddy-ratelimit
-
Deploying Web Apps with Caddy: A Beginner's Guide Caddy
You can rate limit HTTP requests (agnostic of specific HTTP versions): https://github.com/mholt/caddy-ratelimit
-
The Future of Nginx: Getting Back to Our Open Source Roots
If you can't already do it with the rate limit module I wrote, open an issue with your detailed requirements: https://github.com/mholt/caddy-ratelimit -- should be pretty straightforward for the most part.
> QoS for a shared-multitenant system, in the presence of customers with really badly tuned and spiky request workloads, whose traffic you must nevertheless mostly accept.
Yah, we see that sometimes. Caddy usually handles it fine, sometimes with a bit of massaging the config.
- Nginx Modern Reference Architectures
-
Interactive Halloween decorations with raspberry pi's 🎃
I'm using caddy for my web server due to it's awesome automatic certificate functionality using Let's Encrypt behind the scenes. Caddy supports rate limiting via this plugin so I don't have to worry about folks killing my API.
ingress
-
What are the most popular ingress controllers
Caddy
-
Nginx Modern Reference Architectures
That is true, unfortunately. We, the core maintainers, don't use k8s ourselves, so we need to defer to the community for help. See https://github.com/caddyserver/ingress
-
Show HN: Caddy v2.5.0
Caddy at its simplest form is an HTTP server. So you could use it to front end your application that otherwise isn't well suited for taking direct HTTP requests. Caddy would bring you other features like TLS support.
However I think in K8s world Caddy would make the most sense as an Ingress Controller. There is even a project as such: https://github.com/caddyserver/ingress
All traffic would terminate first at Caddy. Handling TLS, HTTP1/2/3, etc. Then passing it back to your application service/pod.
- Cloudflare Proxy Alternative
-
For local projects, do you change your node port range?
Sorry actually I'm mixing up caddy with traefik. And ingress is an http lb + something that talks to k8s to dynamically update the configuration. Caddy has a WIP ingress project https://github.com/caddyserver/ingress
-
Considering (and deciding against) a switch from Traefik to an Envoy-based Ingress Controller
We have an ingress controller in the works by the community here: https://github.com/caddyserver/ingress
What are some alternatives?
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
caddy-authorize - Authorization Plugin for Caddy v2 (JWT/PASETO)
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
xcaddy - Build Caddy with plugins
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
caddy-auth-portal - Authentication Plugin for Caddy v2 implementing Form-Based, Basic, Local, LDAP, OpenID Connect, OAuth 2.0 (Github, Google, Facebook, Okta, etc.), SAML Authentication. MFA with App Authenticators and Yubico.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
pumpkin-pi - Raspberry pi project that controls jack-o-lantern via servo motor and PIR motion sensors
witchonstephendrive.com - A home automation project to control my Halloween decorations
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.