Deploying Web Apps with Caddy: A Beginner's Guide Caddy

• traefik

  183 47,814 9.4 Go

  The Cloud Native Application Proxy

  

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.

• frankenphp

  25 5,785 9.5 Go

  🧟 The modern PHP app server

Depending on the application you can already do this. For example: https://frankenphp.dev/

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• caddy-ratelimit

  4 180 6.5 Go

  HTTP rate limiting module for Caddy 2

You can rate limit HTTP requests (agnostic of specific HTTP versions): https://github.com/mholt/caddy-ratelimit

• nginx-plus-dashboard

  2 14 5.7 HTML
  

1) Nginx Plus and HAProxy have nice consoles to view your thousand upstreams and their current health. The Nginx Plus GUI is Apache 2.0 (https://github.com/nginxinc/nginx-plus-dashboard).

2) Nginx has this concept of rewrite "last" (instead of permanent or temporary)

3) Nginx Plus and HAProxy both have TCP routing OOTB without needing to recompile

4) Nginx and Nginx Plus have more ability to intercept a response from an upstream and modify it vs Caddy's fairly limited handle_response {}

5) Modify body content from upstream seems to require a Caddy module

6) Very difficult to find good Caddy configs and thus why LLMs have such a hard-time helping people with Caddy configs. Having a library of configs would probably help this training

There seems to be an incredible market opportunity for Caddy as I've lost a lost of trust in the Nginx ecosystem and commercial environment. I would get some of these modules into core Caddy so that they are easy to distribute to people used to just installing via apt. And then attack the Nginx Plus features one by one. Add a visual console even though I understand why it doesn't seem like a necessity. I'd love to see Caddy take share and would love to re-allocate my Nginx Plus spend over to Caddy support.

Suggest a related project