Skip to content
stacky

Migrating from Dockge

Stacky reads Dockge’s stack layout unchanged, so there is nothing to convert:

  • one directory per stack in /opt/stacks (or wherever DOCKGE_STACKS_DIR pointed)
  • a compose file named compose.yaml, docker-compose.yaml, docker-compose.yml or compose.yml
  • an optional .env per stack, plus an optional global.env at the root of the stacks directory
  • x-dockge.urls entries, which stacky shows as links

Steps

Section titled “Steps”
  1. Install stacky using the same stacks directory Dockge uses. Both can run side by side because stacky uses port 5005 and Dockge uses 5001.
  2. Open stacky. Every Dockge stack is listed with its live status. Dockge itself shows up too, either as a stack (if its compose file is in the stacks directory) or as an external project.
  3. Deploy a non-critical stack from stacky to confirm everything works.
  4. Stop Dockge from stacky and remove its stack when you’re ready.

Compose projects outside the stacks directory (Dockge called them “not managed by Dockge”) appear in stacky as external projects. Stacky shows their status, logs and shells, but doesn’t edit or deploy them. To manage one from stacky:

  1. Stop it where it lives: docker compose down in its directory.
  2. Move its directory into the stacks directory, e.g. mv ~/apps/media /opt/stacks/media. Fix any absolute paths in the compose file.
  3. Deploy it from stacky.