bootstrap-caddy

Register a local project in Caddy and dnsmasq HTTPS subdomain routing.

1|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/luan/agents --skill bootstrap-caddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap-caddy
Source: https://github.com/luan/agents/tree/main/skills/bootstrap-caddy
Command: npx skills add https://github.com/luan/agents --skill bootstrap-caddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the hassle of manually configuring local HTTPS subdomain routing for a project so you can access it at a stable https://<project>.localhost URL.

Core Features & Use Cases

  • Registers a project route in the local dev-routing system using Caddy + dnsmasq, so the URL stays consistent across sessions.
  • Manages backend port allocation by checking and updating a shared ports.json registry with collision-safe port selection.
  • Optionally wires up the dev server by updating vite.config.ts and environment files when the project source folder exists.

Quick Start

Ask your AI to run bootstrap-caddy for your project name and optional port so it registers https://<project>.localhost and reloads Caddy.

Frequently Asked Questions about bootstrap-caddy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up local HTTPS routing for a Vite project using Caddy?

To set up local HTTPS routing, the system registers your project in a Caddy and dnsmasq routing architecture, assigning a stable https://<project>.localhost URL. It automatically updates vite.config.ts and .env files to align the dev server with the assigned backend port.

How does local subdomain routing handle port collisions across multiple dev projects?

Local subdomain routing prevents port collisions by checking and updating a shared ports.json registry. The system ensures collision-safe port selection so each project maintains a correctly assigned backend port across server restarts.

What infrastructure do I need to run local HTTPS subdomains with dnsmasq and Caddy?

You need an existing dev-routing infrastructure using Caddy and dnsmasq. The process verifies this setup exists, then generates a per-project Caddy site file and reloads the configured Caddyfile to activate the subdomain.

Can I keep the same local URL for my project across different development sessions?

Yes, you can keep the same local URL across sessions. The system registers a permanent route at https://<project>.localhost and manages port allocation in ports.json, ensuring the address stays consistent after project restarts.

Why is my local Caddy configuration not picking up the new project subdomain?

Your local Caddy configuration may not recognize the subdomain if the Caddyfile was not reloaded properly. The routing system addresses this by generating the site file and explicitly reloading Caddy from the configured Caddyfile.