Caddy

What This Skill Does

The Caddy skill for OpenClaw provides an intelligent interface for managing your Caddy web server configurations. It automates the complexities of setting up reverse proxies, handling SSL certificates via automatic HTTPS, and optimizing web traffic routing. By abstracting the Caddyfile syntax, this skill allows users to define site blocks, configure load balancing, and manage containerized services with minimal effort. It acts as an expert assistant, ensuring your configurations are properly formatted, validated, and performance-tuned before they are applied to your infrastructure.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/caddy

Use Cases

1. Internal Service Exposure: Securely expose local Docker services (like Grafana or custom web apps) to the public internet with zero-touch HTTPS.
2. Dynamic Load Balancing: Easily configure upstream backend servers for scalable web applications, leveraging Caddy's built-in passive health checks.
3. Production Web Hosting: Manage complex multi-site configurations where individual domains require specific routing rules, custom headers, and performance optimizations like HTTP/3.
4. Development Environments: Quickly spin up proxy tunnels during the testing phase using Let's Encrypt staging certificates to avoid rate limits.

Example Prompts

1. "Create a Caddyfile for my domain example.com that reverse proxies requests to my local docker container named 'web-app' on port 8080."
2. "How can I enable HTTP/3 and add security headers like X-Frame-Options to my current Caddy configuration?"
3. "Validate my current Caddyfile syntax and then trigger a graceful reload to apply changes without dropping active user connections."

Tips & Limitations

• Indentation is Vital: Caddy is strict about whitespace. Always use the provided validation commands before deploying to production.
• Storage Persistence: In Docker environments, you must mount the /data directory. Failing to do so will result in certificate re-issuance on every container restart, which can hit rate limits.
• Port Conflicts: Ensure ports 80 and 443 are available on the host machine; Caddy requires these to perform ACME challenges even if you only intend to serve HTTPS traffic.
• Use Staging: Always test new configurations against the Let's Encrypt staging environment to protect your domain's reputation and avoid hitting production limits during the experimentation phase.