web-deploy

Deploy local site files to a Caddy static server and report the published URL.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wayne930242/Merlin-My-Pai --skill web-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-deploy
Source: https://github.com/wayne930242/Merlin-My-Pai/tree/main/pai-claude/workspace/.claude/skills/web-deploy
Command: npx skills add https://github.com/wayne930242/Merlin-My-Pai --skill web-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy websites to a Caddy static server, simplifying publishing, updates, and reloads without manual server configuration.

Core Features & Use Cases

  • One-click deployment: Uploads site files from the designated root to Caddy and reloads.
  • URL reporting: Reports the published site URL from merlin-config.json.
  • Environment flexibility: Works for local development and VPS deployments, with simple updates.

Quick Start

Place your site files in /home/pai/merlin/workspace/site/ and run the deployment workflow to publish to Caddy.

Frequently Asked Questions about web-deploy

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

FAQPage Schema
How do I deploy a static website to Caddy without manual server configuration?

To deploy a static website to Caddy, use an automated workflow that uploads site files from a local root, triggers a Caddy reload, and reports the published URL. This removes the need for manual server configuration and simplifies publishing.

What is the best way to reload Caddy after updating static site files?

The best way to reload Caddy after updates is to trigger a server reload via MCP after validating the local site root. This ensures deterministic deployment and quick publish cycles for static websites.

Can I use this deployment workflow for both local development and VPS environments?

Yes, this static website deployment workflow supports both local development and VPS environments. It handles simple domain mapping and centralized configuration across different environments.

How do I get the published website URL after deploying to a static server?

To get the published website URL after deploying to a static server, the workflow reports the address from merlin-config.json. This provides immediate access to the live Caddy site address after deployment.

Do I need to place site files in a specific directory to automate Caddy deployment?

Yes, you need to place your site files in a designated local site root, such as /home/pai/merlin/workspace/site/, to automate Caddy deployment. The workflow validates this root before publishing.

Does this Caddy deployment method support centralized configuration for multiple domains?

Yes, this Caddy deployment method supports centralized configuration and simple domain mapping for static websites. It is applicable to projects requiring quick publish cycles and deterministic deployment workflows.