Merge web container fix into staging

.dockerignore

@@ -1,5 +1,7 @@
 node_modules
 **/node_modules
+.next
+**/.next
 .git
 .gitignore
 *.md
@@ -23,11 +25,15 @@ apps/mcp
 apps/mobile
 apps/supabase
 apps/web
+!apps/web
+!apps/web/**
 e2e
 evidence
 etc
 infra
 scripts
+!scripts
+!scripts/fix-hoisting.js
 terraform
 .agents
 .claude

apps/web/Dockerfile

@@ -12,15 +12,12 @@ ENV NEXT_PUBLIC_POSTHOG_KEY=$NEXT_PUBLIC_POSTHOG_KEY
 ENV NEXT_PUBLIC_POSTHOG_HOST=$NEXT_PUBLIC_POSTHOG_HOST
 ENV NEXT_PUBLIC_API_URL=$NEXT_PUBLIC_API_URL
 
-# Install dependencies
+# Install dependencies from the committed monorepo lockfile.
-COPY package*.json ./
+COPY . .
-RUN npm ci
+RUN npm ci
-
+
-# Copy source code
+# Build the web workspace from the repository root.
-COPY . .
+RUN npm run build -w @sauci/web
-
-# Build the application
-RUN npm run build
 
 # Production stage
 FROM node:20-alpine AS runner
@@ -37,10 +34,11 @@ RUN apk add --no-cache curl
 RUN addgroup --system --gid 1001 nodejs
 RUN adduser --system --uid 1001 nextjs
 
-# Copy built assets from builder
+# Next preserves the workspace path in standalone output. Keep that layout so
-COPY --from=builder /app/public ./public
+# the generated server can resolve its .next directory and public assets.
-COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
+COPY --from=builder --chown=nextjs:nodejs /app/apps/web/.next/standalone ./
-COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
+COPY --from=builder --chown=nextjs:nodejs /app/apps/web/public ./apps/web/public
+COPY --from=builder --chown=nextjs:nodejs /app/apps/web/.next/static ./apps/web/.next/static
 
 USER nextjs
 
@@ -49,4 +47,4 @@ EXPOSE 3000
 ENV PORT=3000
 ENV HOSTNAME="0.0.0.0"
 
-CMD ["node", "server.js"]
+CMD ["node", "apps/web/server.js"]

apps/web/docker-compose.prod.yml

@@ -2,9 +2,9 @@ version: '3.8'
 
 services:
   web:
-    build:
+    build:
-      context: .
+      context: ../..
-      dockerfile: Dockerfile
+      dockerfile: apps/web/Dockerfile
       args:
         - NEXT_PUBLIC_POSTHOG_KEY=${NEXT_PUBLIC_POSTHOG_KEY}
         - NEXT_PUBLIC_POSTHOG_HOST=${NEXT_PUBLIC_POSTHOG_HOST:-https://eu.i.posthog.com}

docs/index.md

@@ -11,6 +11,7 @@ historical notes. Agents should load only the section relevant to their task.
 - [Testing strategy](testing/strategy.md)
 - [Database migration safety](operations/database-migrations.md)
 - [Backend deployment and branching](operations/backend-deployments.md)
+- [Website deployment](operations/web-deployments.md)
 - [Agent routing and effort](agents/routing.md)
 - [Learning promotion](agents/learnings.md)
 - [Authentication](authentication.md)

docs/operations/web-deployments.md

@@ -0,0 +1,26 @@
+# Website deployment
+
+Dokploy deploys the public Sauci website from the `main` branch using
+`apps/web/docker-compose.prod.yml`. The Compose file builds from the repository
+root so the Docker build can use the committed workspace lockfile. Its Dockerfile
+builds `@sauci/web` and runs the Next standalone server from its workspace path.
+
+## Required configuration
+
+`NEXT_PUBLIC_API_URL` is required at build time and must be the intended public
+standalone API URL. `NEXT_PUBLIC_POSTHOG_KEY` is optional. When it is set,
+`NEXT_PUBLIC_POSTHOG_HOST` defaults to `https://eu.i.posthog.com` unless Dokploy
+provides a different value. These public values are inlined into the Next build;
+do not place server credentials in them.
+
+## Promotion and acceptance
+
+Promote the verified website commit to `main` before allowing Dokploy to deploy
+it. After the deployment reports success, verify valid TLS and HTTP 200 for:
+
+- `https://sauci.app/`
+- `https://sauci.app/delete-account`
+
+The second check is required for the Google Play account-deletion resource. A
+successful Dokploy deployment alone is not sufficient evidence that either URL
+is publicly reachable.