Orchestrate mini-app deployment behind a Caddy and PM2 fleet router.
npx skills add https://github.com/TechNickAI/hermes-config --skill mini-app
Please help me install this Agent Skill. Skill: mini-app Source: https://github.com/TechNickAI/hermes-config/tree/main/skills/mini-app Command: npx skills add https://github.com/TechNickAI/hermes-config --skill mini-app
This Skill provides an operator guide to deploy and manage a fleet-local mini-app router stack (Caddy + PM2 + per-app authentication) using the openclaw-config framework, covering install, routing patterns, auth conventions, public exposure via Funnel, and troubleshooting pitfalls.
Add a new mini-app by editing ecosystem.config.js, the Caddyfile, and per-app env vars, then reload PM2 and Caddy.
High-intent search queries and answers about installing and using this skill.
To deploy mini-apps behind a single Caddy router, configure an ecosystem.config.js for PM2 orchestration, update the Caddyfile with routing patterns, set per-app environment variables, and reload both services to apply changes.
Password protection for a mini-app fleet requires setting the APP_PASSWORD environment variable for each specific application within your ecosystem.config.js before reloading the PM2 process manager and Caddy router.
PM2 orchestrates a fleet of mini-apps by managing the lifecycle of each application defined within an ecosystem.config.js file, allowing an operator to start, reload, and monitor all processes simultaneously behind a centralized Caddy router.
Yes, you can expose a locally routed mini-app publicly by configuring Tailscale Funnel within your Caddyfile to route external traffic to the specific internal application endpoint managed by your PM2 fleet.
Caddy router authentication errors for a newly added mini-app typically occur when the APP_PASSWORD or APP_TITLE environment variables are incorrectly configured in the ecosystem.config.js file before the PM2 process was reloaded.
The best way to remove an application from a mini-app fleet router is to delete its configuration block from both the ecosystem.config.js and Caddyfile, clear its environment variables, then reload PM2 and Caddy to update routing.
octave-commonsConfigure PM2 ecosystem.config.js to manage Node.js processes with clustering and auto-restart.
PromakerDevDiagnose and recover failing Dokploy-managed apps using status checks, deploy history, and runtime logs.
shepherdjerredManage Tailscale ingress for private Tailnet and public Funnel exposure.
algansAutomate VPS deployments with SSH, reverse proxy, SSL, and rollback.
