Dockge Removal

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

README.md

@@ -48,7 +48,7 @@ docker run --rm node:22-alpine sh -c \
    node -e \"const h=require('/tmp/gen/node_modules/bcryptjs').hashSync('your-password',12); console.log('MANAGER_PASSWORD_HASH=\\\"'+h.replace(/\\$/g,'\\$\\$')+'\\\"')\""
 ```
 
-### 1. Shared infrastructure — network, MySQL, Caddy, Dockge
+### 1. Shared infrastructure — network, MySQL and Caddy
 
 ```bash
 docker network create next-chair-edge
@@ -60,7 +60,6 @@ Edit `stacks/infra/.env`:
 - `MYSQL_ROOT_PASSWORD` — the first secret you generated above.
 - `MYSQL_HOST_PORT` — set this to `127.0.0.1:3306` so MySQL is only exposed on the VPS loopback interface, not publicly. You can still connect to it remotely through an SSH tunnel.
 - `ACME_EMAIL` — a real address you check (Let's Encrypt renewal notices).
-- `STACKS_DIR` — the absolute clone path, e.g. `/opt/nextchair/stacks`.
 
 ```bash
 docker compose -f stacks/infra/compose.yaml --env-file stacks/infra/.env up -d
@@ -189,3 +188,46 @@ docker compose -f stacks/manager/compose.yaml --env-file stacks/manager/.env up
 ```
 
 If both the business app and Manager changed, do both update steps.
+
+## Upgrading from a version that included Dockge (one-time)
+
+Dockge used to run alongside NextChair Manager as a separate stack
+management UI. It's no longer part of the shared infrastructure stack —
+Manager is the only tool needed to provision and manage business stacks,
+so the two were redundant. If your server was set up before this change,
+existing tenant databases, tenant containers, business Compose files, and
+the global SMTP/VAPID settings are all unaffected — this only removes the
+old Dockge container.
+
+Pull the change, then re-apply the infra stack with `--remove-orphans` so
+Docker removes the container that's no longer defined in
+`stacks/infra/compose.yaml`:
+
+```bash
+cd /opt/nextchair
+git pull
+
+docker compose \
+  -f stacks/infra/compose.yaml \
+  --env-file stacks/infra/.env \
+  up -d --remove-orphans
+```
+
+`--remove-orphans` only removes containers Compose no longer recognizes
+(the old `next-chair-dockge` container) — it does not touch Caddy, MySQL,
+or their volumes.
+
+This does **not** delete Dockge's own data volume
+(`next-chair-dockge-data`) — Docker never removes volumes on its own, and
+this command has no reason to either. Once you've confirmed Caddy, MySQL
+and every business are still healthy, you can remove that now-unused
+volume by hand:
+
+```bash
+docker volume rm next-chair-dockge-data
+```
+
+Finally, `STACKS_DIR` and `DOCKGE_HOST_PORT` in `stacks/infra/.env` were
+only ever used by Dockge and are safe to delete from that file — nothing
+else in the infra stack reads them. (Manager keeps its own separate
+`STACKS_DIR` in `stacks/manager/.env`; leave that one alone.)