菜单
Use this skill when working with hotify-cli for Traefik/Cloudflare app management, deployment, and infrastructure automation. Always prefer hotify HTTP API over SSH/scp when possible.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/javimosch/hotify-cli --skill hotify命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | hotify |
| description | Use this skill when working with hotify-cli for Traefik/Cloudflare app management, deployment, and infrastructure automation. Always prefer hotify HTTP API over SSH/scp when possible. |
Hotify is a CLI+UI tool for managing Traefik/Cloudflare app deployment. It automates DNS setup, SSL certificates, and reverse proxy configuration for web apps.
Core Principle: If an operation can be done via hotify's HTTP API, always prefer it over SSH/scp. This enables true remote management without requiring SSH access to servers.
--target flag (default)setup, add, edit, remove, liststart, stop, restart, status, pause, resumesetup-dns, setup-traefik, basic-authdeploy, deploy-compose, compose-sync, compose-copy-dircomposedockertraefik-systemAll app configuration commands support remote execution via HTTP API:
# Remote mode (default - uses configured target)
hotify-cli basic-auth --id myapp --action list
hotify-cli setup-traefik --id myapp
hotify-cli setup-dns --id myapp
# Explicit target specification
hotify-cli basic-auth --id myapp --action list --target dk1
hotify-cli setup-traefik --id myapp --target dk1
# Local mode (execute directly on local server)
hotify-cli basic-auth --id myapp --action list --local
hotify-cli setup-traefik --id myapp --local
hotify setup --id <id> --name <n> --domain <d> --port <p> --cmd <c> [--backend-url <url>] [--target <t> | --local] — Create or update apphotify add --id <id> --name <n> --domain <d> --port <p> --cmd <c> [--backend-url <url>] [--target <t> | --local] — Strict create (fails if exists)hotify remove --id <id> [--target <t> | --local] — Delete apphotify list [--target <t> | --local] — List all appshotify start --id <id> — Start app (uses configured target by default)hotify stop --id <id> — Stop apphotify restart --id <id> — Restart apphotify status --id <id> — App statushotify pause --id <id> — Pause app (SIGSTOP)hotify resume --id <id> — Resume paused app (SIGCONT)hotify setup-dns --id <id> [--ip <ip>] — Create/update Cloudflare DNS A recordhotify setup-traefik --id <id> [--challenge-type http|dns] — Configure Traefik routinghotify basic-auth --id <id> --action <add|remove|list> — Manage Traefik HTTP basic authhotify deploy-compose --id <id> --source <dir> [--target <t> | --local] — Copy full project tree to remotehotify compose-sync --id <id> [--source <dir>] [--target <t> | --local] — Sync compose file (+ .env) onlyhotify compose-copy-dir --id <id> --dir <subdir> --source <local-dir> [--target <t> | --local] — Copy directory to remotehotify compose [--id <app>] [--target <t> | --local] <subcommand> [args...] — Passthrough to docker compose (v2.10.0 adds remote support)hotify deploy --id <id> --source <path> [--target <t> | --local] — Deploy binary/folder (v2.10.0 adds --local)hotify prune --id <id> [--target <t> | --local] — Remove DNS/Traefik for app (v2.10.0 adds remote support)hotify auth --url <u> --token <t> --name <n> — Authenticate with remote daemonhotify targets --action list — List targetshotify targets --action use --name <n> — Set active targethotify api-keys --action add --name <n> [--permissions <p>] — Create API key with permissionshotify api-keys --action list — List all API keyshotify api-keys --action remove --name <n> — Remove API keyhotify api-keys --action permissions --name <n> --add <p> --remove <p> — Update permissionshotify api-keys --action usage --name <n> — Show API key usage statisticsAvailable Permissions: deploy, start, stop, restart, logs, config, admin, all, *
Note: Permissions are fully enforced at server level as of v2.7.4. Use all or * for full access.
Hotify-cli supports external reverse proxy targets, allowing apps to run on different machines while hotify handles DNS, TLS, and Traefik routing.
# Setup app with external backend URL
hotify-cli setup \
--id myapp \
--name "My App" \
--domain myapp \
--port 3000 \
--cmd "/usr/local/bin/myapp start" \
--backend-url "http://100.114.4.57:8080"
When --backend-url is set:
http://127.0.0.1:<port># App running on remote container via Tailscale
hotify-cli setup \
--id remote-app \
--name "Remote App" \
--domain app.example.com \
--port 3000 \
--cmd "/usr/local/bin/app start" \
--backend-url "http://<tailscale-ip>:3000"
# Setup DNS and Traefik
hotify-cli setup-dns --id remote-app
hotify-cli setup-traefik --id remote-app
Service Binding for Remote Access
ss -tlnp | grep <port>ACME Certificate Generation Timing
/etc/traefik/acme.jsonLocal Flag for DNS/Traefik Setup
--local flag to execute commands directly on local machinehotify-cli setup-dns --id <app> --ip <ip> --localDomain Naming Patterns
<service>.<machine>.<domain>hermes.rbm21.intrane.fr, cmdcenter.dk1.intrane.frhotify-cli start -daemon): HTTP server on port 8080 with embedded web UI + REST API✅ Permission Enforcement Implemented: As of v2.7.4, hotify-cli enforces permissions at the server level. The auth middleware validates tokens AND checks specific permissions for each endpoint.
Current State:
deploy, start, stop, restart, logs, config, adminall or * grants full accessPermission Mapping:
/api/status → requires logs/api/config → requires config/api/apps/*/start → requires start/api/apps/*/stop → requires stop/api/deploy → requires deploy/api/api-keys/* → requires adminWildcard Usage:
# Create full access key using wildcard
hotify-cli api-keys --action add --name fullaccess --permissions all
# Alternative wildcard syntax
hotify-cli api-keys --action add --name fullaccess --permissions "*"
Recommendation for Agents:
all/*) only for trusted administrative accessImplementation Details:
permissions.goEndpointPermissions arrayCheckTokenPermission, CheckTokenPermissionsserver.go enforces permissions per endpointParsePermissions and AddKey functionsCurrent version: v2.10.0
deploy, deploy-compose, compose-sync, compose-copy-dir, volume-init, setup-compose) now accept --local to execute directly on current machine without remote targetsetup, add, edit, remove, list all support --target for remote execution via HTTP API
POST /api/remote/apps/{id}/config-setup, GET|DELETE /api/remote/apps/{id}/configSetupAppConfig, GetAppConfig, RemoveAppConfig, ListAppsRemotedocker subcommands (list, start, stop, restart, status, logs, enable-traefik, disable-traefik) support --target / --local
DockerListRemote, DockerStartRemote, DockerStopRemote, DockerRestartRemote, DockerStatusRemote, DockerLogsRemote, DockerEnableTraefikRemote, DockerDisableTraefikRemoteprune --target <name> sends prune operation to remote daemon, --local forces local execution
POST /api/remote/apps/{id}/prunecompose --target <name> routes docker compose commands to remote daemon, --local forces local execution
POST /api/remote/compose/exec with subcommand allowlist and audit loggingComposeExecRemote--backend-url parameter for proxying remote services--local flag support for DNS and Traefik commandsall/*) for full access keysbasic-auth, setup-traefik, setup-dns commands--target and --local flags for app configuration commands# 1. Register app
hotify-cli setup --id myapp --name "My App" --domain myapp --port 3000 --cmd "/usr/local/bin/myapp start"
# 2. Setup DNS (remote)
hotify-cli setup-dns --id myapp
# 3. Setup Traefik (remote)
hotify-cli setup-traefik --id myapp
# 4. Deploy and start (remote)
hotify-cli deploy --id myapp --source ./myapp
hotify-cli start --id myapp
# 1. Register app with compose config
hotify-cli setup --id cmdcenter --name "Command Center" --domain cmdcenter --port 3031 \
--cmd "docker compose up -d" --compose-file compose.binary.yml --compose-path /home/dk1/cmdcenter
# 2. Deploy project files (remote)
hotify-cli deploy-compose --id cmdcenter --source /local/path/to/project
# 3. Start compose stack (remote)
hotify-cli compose --id cmdcenter up -d
main.go - CLI entry pointconfig.go - Configuration managementserver.go - HTTP server and API endpointsdeploy_client.go - HTTP client for remote operationsbasic_auth.go - Basic auth managementdns_traefik_cli.go - DNS and Traefik CLI commandsserver_apps_remote.go - Remote API endpoints for app operationsAGENTS.md - Comprehensive agent documentationSmoke tests are performed on dk1@92.113.145.178. All remote execution commands should be tested with both --target and --local flags.
--local flag only when executing on the same machine as the hotify daemon--human for human-readable text