caddy

Caddy automatic HTTPS web server. Use for simple web serving.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

caddy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Caddy automatic HTTPS web server. Use for simple web serving.

Teams using caddy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/caddy/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/caddy/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/caddy/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How caddy Compares

Feature / Agent	caddy	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Caddy automatic HTTPS web server. Use for simple web serving.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Caddy

Caddy 2 is a powerful, enterprise-ready web server with **automatic HTTPS** by default. v2.8 (2025) improves **HTTP/3** performance and certificate management.

## When to Use

- **HTTPS Default**: You want zero-config SSL. Caddy obtains and renews certificates automatically.
- **Simplicity**: `Caddyfile` is the most human-readable config format.
- **Go Apps**: Can act as a process manager or library for Go applications.

## Quick Start

```caddyfile
# Caddyfile
example.com {
    reverse_proxy localhost:3000
    encode zstd gzip
    file_server
}
```

## Core Concepts

### Caddyfile

Simple configuration format.
`directive argument { block }`

### JSON Config

The native config format. Caddyfile is adapted to JSON. API allows real-time config updates via REST.

### Modules

Caddy is extensible. Plugins (like `caddy-dns-cloudflare`) are compiled in via `xcaddy`.

## Best Practices (2025)

**Do**:

- **Use Caddyfile**: For 99% of cases, it's enough.
- **Persist /data**: Caddy stores certificates in the `/data` directory. Mount this volume in Docker.
- **Use `caddy fmt`**: Auto-format your config.

**Don't**:

- **Don't sit behind another proxy**: If you hide Caddy behind Cloudflare/Nginx, you break its ACME challenges unless you configure it specifically.

## References

- [Caddy Documentation](https://caddyserver.com/docs/)