Agent skill · software engineering · thienanblog
vps-docker-traefik-deploy
Coordinator-routed specialist for production Docker Compose deployment on self-hosted VPS or cloud servers with Traefik, DNS, registries, storage, backups, rollback, and host hardening. Use after project-development-mindset makes production deployment primary, or directly when explicitly invoked or installed standalone. Do not use for local Docker development, deployment-adjacent app changes, or generic cloud hosting.
Why this skill is useful
Adds detailed deployment plans and scripts for secure Docker and Traefik setups that are not commonly found in public documentation.
What it needs
Requires docker, docker-compose installed locally. About 2k tokens when loaded. Last updated 2026-08-05. 63 stars on the source repository.
What this skill does
VPS Docker Traefik Deploy Overview Use this skill to turn an application stack into a real production deployment plan with secure host setup, reverse proxying, registry-based releases, private admin access, persistent storage, backups, and rollback. Run this skill in the main conversation. Do not spawn subagents, agent teams, or delegated parallel workers unless the user explicitly approves the proposed count and scope after being told that doing so can increase usage. Ask again before expanding an approved scope. Prefer Ubuntu LTS or Debian stable. Prefer immutable image tags. Prefer Traefik for public ingress and SSH tunnels for admin-only access. Workflow 1. Establish facts before changing anything. 2. Minimize the public network surface. 3. Baseline the host with a non-root operator account. 4. Install Docker from the official stable channel. 5. Deploy Traefik separately from the app stack. 6. Keep state outside container writable layers. 7. Deploy app images by pull, not by rebuilding on the server. 8. Validate health, backup, restore, rollback, and pruning. Establish Facts Confirm these points first: operating system and version public domains and subdomains TLS strategy: HTTP challenge or DNS challenge public services: website, API, websocket, admin UI, registry private services: database, Redis, dashboards registry type: managed or self-hosted persistent data locations backup destination and retention restore expectations whether a single VPS is still acceptable If the project already has deployment docs, read them first and treat them as the application-specific contract. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thienanblog/vps-docker-traefik-deploy