Caddy

Back

Something new to me, and it will be important in the future.

Caddy is a modern web server, similar to Nginx or Apache HTTP Server—but with a very different philosophy.

⚡ Why Caddy is getting popular

1. Automatic HTTPS (this is the big deal)

  • With Nginx/Apache, you manually configure SSL using Let’s Encrypt
  • With Caddy → HTTPS is automatic
  • You literally write:example.com
    reverse_proxy localhost:3000    and it handles SSL, renewals, redirects

2. Simpler config (human-readable)
Caddy uses a Caddyfile:

example.com {
  root * /var/www/html
  file_server
}

Compare that to Nginx configs… much cleaner.

3. Built-in reverse proxy
Great for:

  • Node apps
  • Docker containers
  • APIs

You don’t need extra setup—it just works.

4. HTTP/3 + modern defaults

  • Caddy ships with modern protocols enabled by default
  • Nginx often needs tuning

🧠 When it actually matters (for you)

Since you’re:

  • running servers (you showed SSH + nginx config earlier)
  • building projects like dharan.city

Caddy can simplify your life in:

  • quick deployments
  • staging servers
  • small SaaS projects
  • local dev setups

⚠️ But don’t blindly switch

Caddy is great, but:

  • Nginx is still more widely used in production
  • Some advanced configs are easier in Nginx
  • Tutorials & community are bigger for Nginx

Think of it like:

  • Nginx = industry standard
  • Caddy = developer-friendly future

🔥 Practical advice (important)

Don’t replace everything yet.

Instead:

  • Keep your current Nginx setup
  • Spin up one test project using Caddy
  • Try:
    • reverse proxy
    • HTTPS auto setup
    • simple WordPress or Node app

If you want, I can give you:

  • a 1-command install + run setup
  • or convert your existing nginx config → Caddyfile

That’s the fastest way to actually feel why it matters.