static-deploy

Deploy static HTML/JS/CSS sites using Caddy or nginx Dockerfile patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nixopus/agent --skill static-deploy-nixopus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: static-deploy
Source: https://github.com/nixopus/agent/tree/main/skills/static-deploy
Command: npx skills add https://github.com/nixopus/agent --skill static-deploy-nixopus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys static sites using Caddy or nginx with Staticfile-based configuration.

Core Features & Use Cases

  • Supports static HTML/JS/CSS without backend code, with optional Staticfile root and custom Caddyfile when needed.
  • Provides Dockerfile patterns for nginx and Caddy deployments to containerize static sites.
  • Use Case: Deploy a SPA or static site quickly by including index.html and Staticfile at project root and choosing a serving container.

Quick Start

Run a static-site deployment by placing index.html or Staticfile at the project root and choosing an nginx or Caddy Dockerfile pattern.

Frequently Asked Questions about static-deploy

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

FAQPage Schema
How do I deploy a static site using Docker with nginx or Caddy?

To deploy static sites, place index.html or a Staticfile at the project root and select a provided nginx or Caddy Dockerfile pattern to containerize and serve your HTML, JS, and CSS assets.

What is a Staticfile and when do I need it for static site deployment?

A Staticfile specifies the root directory configuration for deploying pure HTML, JS, and CSS projects without server-side runtimes, standardizing hosting with Caddy or nginx containers.

Can I use this approach to deploy a single-page application built with only HTML and JavaScript?

Yes, you can deploy a single-page application by placing your built index.html and static assets at the project root and selecting an nginx or Caddy serving container template.

What is the best way to configure Caddy for serving a static HTML site?

The best way to configure Caddy is using a Staticfile at the project root for default settings, with an option to provide a custom Caddyfile alongside the Dockerfile pattern when needed.

Does this static site deployment method support backend runtimes like Node.js or Python?

No, this deployment method does not support server-side runtimes. It is strictly designed for projects that serve pure HTML, JS, and CSS without backend code, using Caddy or nginx containers.

Why should I choose between nginx and Caddy for containerized static hosting?

Choosing between nginx and Caddy depends on your serving preferences; both provide Dockerfile patterns to standardize containerized hosting for static sites, while Caddy allows optional custom Caddyfile configuration.