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>

.env.example

@@ -72,5 +72,17 @@ VITE_APP_NAME="${APP_NAME}"
 # Uploads: each encrypted chunk the browser sends, in MB
 # UPLOAD_CHUNK_SIZE_MB=16
 
-# Docker (used only when deploying with docker-compose.yml)
+# Docker development: `docker compose up` runs this file. On OrbStack, also set
+# APP_URL=https://app.sealshare.orb.local and VITE_DEV_SERVER_URL=https://vite.sealshare.orb.local.
+# Without OrbStack, append :docker-compose.ports.yml and set APP_URL=http://localhost:8000.
+COMPOSE_FILE=docker-compose.dev.yml
+
+# Where the browser reaches the Vite dev server, when not on http://localhost
+# VITE_DEV_SERVER_URL=https://vite.sealshare.orb.local
+
+# Ports on this machine: the Vite dev server's, and the app's with docker-compose.ports.yml
+# VITE_PORT=5173
+# APP_PORT=8000
+
+# Docker production (docker compose -f docker-compose.yml), with AUTO_HTTPS=true
 # SERVER_NAME=share.example.com