Cadder

Cadder coordinates local Caddy reverse proxies that would otherwise fight for the same HTTP and HTTPS ports. Projects can keep using a caddy run workflow, while Cadder registers them with one per-user daemon and applies the active configs through one real Caddy process.

Published documentation: https://maxie.dev/Cadder/

What's included

Cadder ships three executables:

• caddy is the Caddy-compatible shim. For caddy run, it starts or connects to cadderd, registers the current project's Caddyfile, keeps that registration alive while the shim process runs, and unregisters on exit. Other Caddy commands are delegated to the safely resolved real Caddy binary.
• cadderd is the per-user daemon. It owns local IPC, entrypoint registrations, adapted Caddy config composition, the generated effective runtime config, the real Caddy process it starts, diagnostics, and bounded log storage.
• cadder-tui is the terminal UI. It connects to the daemon, can start it unless --no-start is used, and shows overview state, entrypoints, domains, per-domain logs, diagnostics, filters, toggles, log export, and daemon shutdown.

Each executable supports --help and --version.

Quick use

1. Download the latest Cadder release for your operating system from GitHub Releases.
2. Create cadder.toml next to Cadder with the path to the real Caddy binary.
3. Run a project through Cadder's caddy shim.
4. Open cadder-tui for state, domains, logs, and diagnostics.

Full setup docs:

• Getting started
• cadder.toml
• How to use
• Real Caddy resolution

Commands

caddy run
cadder-tui

For a local checkout, run the project checks with:

cargo fmt --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo run -p xtask -- check

Contributing

See CONTRIBUTING.md, SECURITY.md, and docs/ARCHITECTURE.md for repository workflow, security reporting, and architecture notes.

License

Cadder is licensed under the terms in LICENSE.