caddy-reverse-proxy
di brennerspear
Web & Frontend DevelopmentSintesi
Add, manage, and troubleshoot Caddy reverse proxy routes for local apps via wildcard subdomains.
Descrizione
Cosa fa questa skill
Routes *.YOUR_DOMAIN wildcard subdomains to local services via Caddy reverse proxy with automatic Let's Encrypt HTTPS certificates. Access is limited to Tailscale, keeping services off the public internet. Supports macOS (LaunchDaemon) and Linux (systemd).
Manages wildcard TLS certs and subdomain routing in a single Caddyfile without exposing services publicly.
Quando usarla
- Serving a local web app at a named HTTPS subdomain
- Adding a new self-hosted tool to a private Tailscale network
- Reloading Caddy routing config without a full service restart
- Diagnosing cert failures after a Vercel API token expires
- Spinning up a dev server with automatic subdomain and TLS
Esempio di workflow
User asks: Add a reverse proxy for my local app running on port 3100
- 1
Creates a background service definition (LaunchAgent or systemd unit) for the app
- 2
Adds a Caddyfile block for appname.YOUR_DOMAIN pointing to localhost:3100
- 3
Appends a dashboard HTML entry for the new subdomain
- 4
Reloads Caddy config via the admin API
- 5
Confirms TLS cert provisioned after the 30-60 second DNS-01 challenge
App is accessible at https://appname.YOUR_DOMAIN over Tailscale with a valid TLS certificate
Requisiti
- Caddy installed with the caddy-dns/vercel plugin
- Tailscale account with Tailscale running on the host
- Vercel account with a domain managed by Vercel DNS
- Vercel API token with DNS edit permissions
Installazione
clawhub install brennerspear/caddy-reverse-proxyEsegui il comando CLI oppure incolla il prompt in Claude Code, Cursor, Codex o nell'agente di coding che usi.