Dockge Removal

Removed dockge from the app as it is not required due to the manager page picking up most of its abilities.

stacks/blake-heritage/compose.yaml

@@ -1,8 +1,8 @@
 name: next-chair-blake-heritage
 
 # One business's app container on the shared multi-business VPS setup —
-# see stacks/infra/compose.yaml for the shared MySQL/Caddy/Dockge this
-# attaches to, and that file's header for the exact one-time setup steps
+# see stacks/infra/compose.yaml for the shared MySQL/Caddy this attaches
+# to, and that file's header for the exact one-time setup steps
 # (create this business's database, copy .env.business.example, add a
 # Caddy site file) needed before this file can start.
 #

stacks/infra/compose.yaml

@@ -1,24 +1,24 @@
 name: next-chair-infra
 
 # Shared infrastructure for the multi-business VPS deployment: Caddy
-# (reverse proxy + automatic TLS via Let's Encrypt), one MySQL server
+# (reverse proxy + automatic TLS via Let's Encrypt) and one MySQL server
 # shared by every business (a separate database + user per business, NOT
-# one shared schema — see step 1 below), and Dockge (a web UI for
-# starting/stopping/inspecting these compose stacks by hand).
+# one shared schema — see step 1 below).
 #
-# Lives in stacks/infra/ so Dockge (which expects one directory per
-# stack, each with its own compose.yaml) can manage this stack too —
-# see stacks/blake-heritage/, stacks/marios/ for the same shape per
-# business. Deliberately separate from docker-compose.local.yaml at the
+# Lives in stacks/infra/, one directory per stack (each with its own
+# compose.yaml) — see stacks/blake-heritage/, stacks/marios/ for the same
+# shape per business, and stacks/manager/ for the management UI's own
+# stack. Deliberately separate from docker-compose.local.yaml at the
 # repo root, which is the single-business local/Docker-Desktop setup and
 # stays untouched by any of this.
 #
+# Stack management/provisioning is handled by NextChair Manager (see
+# manager/ at the repo root) — there is no separate stack-management UI
+# alongside it.
+#
 # ── One-time setup ───────────────────────────────────────────────────────
 #   docker network create next-chair-edge
-#   cp .env.infra.example stacks/infra/.env   (then fill in real values —
-#     in particular STACKS_DIR must be this repo's absolute path on the
-#     VPS, e.g. /opt/nextchair/stacks — see the STACKS_DIR comment in that
-#     file for why it can't just be a relative path here)
+#   cp .env.infra.example stacks/infra/.env   (then fill in real values)
 #   docker compose -f stacks/infra/compose.yaml --env-file stacks/infra/.env up -d
 #
 # ── Per business ──────────────────────────────────────────────────────
@@ -98,28 +98,6 @@ services:
     networks:
       - next-chair-edge
 
-  dockge:
-    image: louislam/dockge:1
-    container_name: next-chair-dockge
-    restart: unless-stopped
-    env_file:
-      - .env
-    environment:
-      DOCKGE_STACKS_DIR: "${STACKS_DIR}"
-    ports:
-      - "${DOCKGE_HOST_PORT:-5001}:5001"
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - next-chair-dockge-data:/app/data
-      # MUST be mounted at the identical absolute path on both host and
-      # container — see the STACKS_DIR comment in .env.infra.example for
-      # why (Dockge shells `docker compose` out to the HOST's dockerd via
-      # the socket above, so a compose-file path only means the same
-      # thing on both sides if the bind-mount doesn't change it).
-      - "${STACKS_DIR}:${STACKS_DIR}"
-    networks:
-      - next-chair-edge
-
 volumes:
   next-chair-mysql-data:
     name: next-chair-mysql-data
@@ -127,8 +105,6 @@ volumes:
     name: next-chair-caddy-data
   next-chair-caddy-config:
     name: next-chair-caddy-config
-  next-chair-dockge-data:
-    name: next-chair-dockge-data
 
 networks:
   next-chair-edge:

stacks/manager/compose.yaml

@@ -4,8 +4,8 @@ name: next-chair-manager
 # explains why it's a fully separate app). Its own stack, separate from
 # stacks/infra/compose.yaml, since this is real application code that
 # gets rebuilt/updated far more often than the off-the-shelf infra
-# images (MySQL, Caddy, Dockge) — a code change here shouldn't require
-# touching the infra stack at all.
+# images (MySQL, Caddy) — a code change here shouldn't require touching
+# the infra stack at all.
 #
 #   cp manager/.env.example stacks/manager/.env   (then fill in real values)
 #   docker compose -f stacks/manager/compose.yaml --env-file stacks/manager/.env up -d --build