Manage Docker Compose stacks on self-hosted Composer via REST API.
npx skills add https://github.com/erfianugrah/dotfiles --skill composer-erfianugrah
Please help me install this Agent Skill. Skill: composer Source: https://github.com/erfianugrah/dotfiles/tree/main/.pi/agent/skills/composer Command: npx skills add https://github.com/erfianugrah/dotfiles --skill composer-erfianugrah
It helps you reliably deploy, update, restart, and remove Docker Compose stacks on a self-hosted Composer platform without running local compose commands that might target the wrong host or leak sensitive operations onto the wrong machine.
Ask the AI to list your stacks on the production instance using COMPOSER_API_KEY and the Composer base URL by running a curl GET to /api/v1/stacks.
High-intent search queries and answers about installing and using this skill.
You can manage Docker Compose stacks remotely via a REST API by targeting a self-hosted Composer instance to perform CRUD operations, deployments, and environment reconciliation without running local compose commands. This prevents accidental operations on the wrong host.
The safest way to automate Docker Compose deployments on a production host is to use API-driven orchestration with enforced auth roles and production guardrails, ensuring you never run the composerd daemon directly on your dev machine.
You can stream logs and pipeline runs for Docker Compose operations by utilizing real-time SSE streams provided by the Composer platform, allowing you to monitor async jobs and event-driven pipeline executions over the API.
You orchestrate pipelines with Docker Compose actions and shell commands by defining event-driven or scheduled pipelines on the Composer platform, chaining compose actions, docker exec, and HTTP requests within allowed operational guardrails.
API requests deploying Docker Compose stacks may be blocked by WAF rules intercepting credential-shaped bodies. The Skill provides specific WAF workarounds to ensure security-critical credential handling passes correctly during stack automation.
Yes, the Composer API relies on OpenAPI-driven endpoint discovery to ensure safe targeting and spec-driven automation, requiring correct API authentication via API key, cookie, or bearer token to manage stack lifecycles.
mnltManage n8n workflows and executions via its REST API.
sandgardenhqMonitor sgai workspaces and agent activity via HTTP and SSE endpoints.
linanwxOrchestrate Docker container and image lifecycle tasks with deterministic commands.
mfzzfBootstrap a full-stack app with Go, Next.js, PostgreSQL, and Docker Compose.
