Run development on the production stack with a Vite dev server

docker-compose.dev.yml extends docker-compose.yml, so development runs the
scheduler too, and takes its settings from .env, which selects the file
through COMPOSE_FILE. The dev image is a stage of the Dockerfile and shares
the production image's PHP extensions; the app listens on port 80 as in
production.

A vite service runs the dev server with hot reload. No ports are published:
OrbStack serves https://app.sealshare.orb.local and
https://vite.sealshare.orb.local, with the ports pinned by label. Without
OrbStack, docker-compose.ports.yml publishes APP_PORT and VITE_PORT on
127.0.0.1. vite.config.js takes the dev server's address from
VITE_DEV_SERVER_URL and listens on IPv4 and IPv6, as OrbStack's proxy
connects over either.

Each start installs Composer packages, clears caches, migrates and links
storage.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docker-compose.ports.yml

@@ -0,0 +1,20 @@
+# ============================================
+# SealShare - Development ports (layered on docker-compose.dev.yml)
+# ============================================
+#
+# Publishes the app and the Vite dev server on this machine, for Docker without OrbStack's domains:
+#   COMPOSE_FILE=docker-compose.dev.yml:docker-compose.ports.yml
+#   APP_URL=http://localhost:8000
+#
+# Bound to 127.0.0.1: a debug build does not belong on the network.
+#
+# ============================================
+
+services:
+  app:
+    ports:
+      - "127.0.0.1:${APP_PORT:-8000}:80"
+
+  vite:
+    ports:
+      - "127.0.0.1:${VITE_PORT:-5173}:${VITE_PORT:-5173}"