Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

dockge

Estrellas0

Forks0

Actualizado29 de junio de 2026 a las 20:30

Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Redth

Redth/homelab-assist

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

SKILL.md

readonly

name	dockge
description	Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

Dockge

Dockge (https://github.com/louislam/dockge) is a lightweight, file-based compose manager. It's popular in homelabs but, unlike Dockhand/Portainer, exposes no documented REST API and no MCP server — its UI talks over Socket.IO. Practical management therefore leans on the filesystem (and SSH). Obey the homelab-core:homelab-safety skill and load docker-compose-stacks.

The model

Stacks live as real files: ${DOCKGE_STACKS_DIR} (default /opt/stacks), one dir per stack containing compose.yaml + .env.
Because stacks are plain files, they're friendly to Git/backup and to direct editing — but edits and deploys generally happen via the Dockge UI or on the host filesystem.
Agent system (v1.4.0+) lets one Dockge manage multiple hosts, each with its own /opt/stacks.

Working with it

Since there's no API/MCP:

Read: you can read compose.yaml/.env under /opt/stacks/<name> and docker compose ps/logs to inspect — read-only, fine.
Change a stack: editing the compose file on disk and (re)deploying is a host filesystem operation → treat as significant. If it requires SSH to the host, clear the SSH-confirmation gate (homelab-core:homelab-safety) and follow the SSH execution discipline (homelab-core:homelab-ssh): confirm the host, back up the compose/.env before editing, validate with docker compose config, then deploy via the Dockge UI or docker compose up -d in that stack dir. Keep the UI and disk in sync.
Prefer the UI for deploy/stop when the user has it open, to avoid the UI showing stale state.

When to steer toward Dockhand

The user prefers Dockhand. If a task needs reliable programmatic control (bulk changes, automation, multi-host orchestration), note that Dockge's lack of an API makes it awkward and Dockhand/Portainer are better suited — surface that trade-off rather than silently doing fragile filesystem surgery.

Build opportunity

A Dockge MCP server doesn't exist (its Socket.IO interface makes it harder). If Dockge automation becomes important, building one is a candidate under the repo's hybrid MCP strategy — note it.

Safety checklist

Identify the stack dir and host → read current files first → for edits, confirm the SSH/filesystem change → back up the compose/.env before editing → summarize + approve → deploy → verify health.

Más de este repositorio

mismo repositorio

dockhand

Redth/homelab-assist

Manage Docker via Dockhand — the preferred control plane in this homelab — and its Hawser remote agents. Covers the Dockhand architecture (central server + Hawser Standard/Edge agents), how to drive it (the mcp-dockhand MCP server or its REST API), compose-stack and container operations, multi-host/environment targeting, and Git-synced stacks. Load this when the user manages Docker with Dockhand.

2026-07-010

docker-compose-stacks

Redth/homelab-assist

Shared foundational knowledge for working with Docker Compose stacks — the compose file format, services/networks/volumes/secrets, environment and .env handling, healthchecks, common operations (up/down/pull/logs/ps), and safe-change practices. Load this for any compose-based work, alongside the control-plane skill (Dockhand/Portainer/Dockge) that actually applies the changes.

2026-06-290

docker-on-proxmox

Redth/homelab-assist

Understand and troubleshoot a Docker host running inside Proxmox — as a VM or as a privileged/unprivileged LXC — and how VLAN networking, macvlan/ipvlan, VLAN-aware bridges, and passed-through/bind-mounted storage interact across the Proxmox and Docker layers. Load this when a Docker networking or storage problem may originate at the Proxmox layer, or when planning how to host Docker on Proxmox.

2026-06-290

docker-overview

Redth/homelab-assist

Entry point and router for managing Docker in a homelab. Load this first for any Docker request — it identifies which control plane is in use (Dockhand preferred, or Portainer/Dockge/raw Engine), establishes the version check, and routes to the right skill (compose stacks, Dockhand, reverse-proxy label routing, or Docker-on-Proxmox networking).

2026-06-290

npm-reverse-proxy

Redth/homelab-assist

Set up and manage domain routing for homelab services using nginx-proxy-manager (NPM) driven by Docker container labels via npm-docker-sync. Load this when the user wants to expose a container/stack at a domain, debug why a service isn't routing, or understand the label-based proxy-host automation pattern. Covers the npm.* label scheme, how sync maps containers to NPM proxy hosts, and SSL/forced-host details.

2026-06-290

portainer

Redth/homelab-assist

Manage Docker (and Kubernetes) via Portainer's REST API or the official portainer-mcp server — environments/endpoints, stacks, containers/images/networks/volumes, and the Docker API proxy. Load this when the user manages Docker with Portainer rather than Dockhand.

2026-06-290

name	dockge
description	Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

Dockge

The model

Stacks live as real files: ${DOCKGE_STACKS_DIR} (default /opt/stacks), one dir per stack containing compose.yaml + .env.
Because stacks are plain files, they're friendly to Git/backup and to direct editing — but edits and deploys generally happen via the Dockge UI or on the host filesystem.
Agent system (v1.4.0+) lets one Dockge manage multiple hosts, each with its own /opt/stacks.

Working with it

Since there's no API/MCP:

Read: you can read compose.yaml/.env under /opt/stacks/<name> and docker compose ps/logs to inspect — read-only, fine.
Change a stack: editing the compose file on disk and (re)deploying is a host filesystem operation → treat as significant. If it requires SSH to the host, clear the SSH-confirmation gate (homelab-core:homelab-safety) and follow the SSH execution discipline (homelab-core:homelab-ssh): confirm the host, back up the compose/.env before editing, validate with docker compose config, then deploy via the Dockge UI or docker compose up -d in that stack dir. Keep the UI and disk in sync.
Prefer the UI for deploy/stop when the user has it open, to avoid the UI showing stale state.

When to steer toward Dockhand

Build opportunity

A Dockge MCP server doesn't exist (its Socket.IO interface makes it harder). If Dockge automation becomes important, building one is a candidate under the repo's hybrid MCP strategy — note it.