docker-compose.yml

version: "3.9"

services:
  nexus-main:
    build: .
    container_name: nexus-main
    restart: unless-stopped
    ports:
      - "8080:8080"
      - "8765:8765"
  nexus-staging:
    build: .
    container_name: nexus-staging
    restart: unless-stopped
    ports:
      - "8081:8080"
      - "8766:8765"
[claude] Live staging + auto-refresh on push (#33) (#34) Co-authored-by: Claude (Opus 4.6) <claude@hermes.local> Co-committed-by: Claude (Opus 4.6) <claude@hermes.local> 2026-03-24 01:30:28 +00:00			`version: "3.9"`

			`services:`
fix: align docker-compose.yml with deploy.sh services 2026-04-13 00:26:55 +00:00			`nexus-main:`
[claude] Live staging + auto-refresh on push (#33) (#34) Co-authored-by: Claude (Opus 4.6) <claude@hermes.local> Co-committed-by: Claude (Opus 4.6) <claude@hermes.local> 2026-03-24 01:30:28 +00:00			`build: .`
fix: align docker-compose.yml with deploy.sh services 2026-04-13 00:26:55 +00:00			`container_name: nexus-main`
[claude] Live staging + auto-refresh on push (#33) (#34) Co-authored-by: Claude (Opus 4.6) <claude@hermes.local> Co-committed-by: Claude (Opus 4.6) <claude@hermes.local> 2026-03-24 01:30:28 +00:00			`restart: unless-stopped`
			`ports:`
feat: unified HTTP+WS server for proper URL deployment Closes #1339. The Nexus Three.js app required HTTP serving for module imports to work (file:// and raw Forge URLs break). This change: - server.py: dual-purpose async server — HTTP on :8080 (static files) and WebSocket on :8765 (broadcast gateway), single process - Dockerfile: exposes both 8080 (HTTP) and 8765 (WS), includes all frontend assets (boot.js, bootstrap.mjs, gofai_worker.js, etc.) - docker-compose.yml: maps HTTP :8080/:8081 + WS :8765/:8766 - deploy.sh: updated for new port layout - run.sh: standalone no-Docker launcher - app.js: WS URL derives from HTTP port (8080->8765, 8081->8766) - deploy.yml workflow: docker compose on remote host To deploy: `./deploy.sh` (Docker) or `./run.sh` (bare metal). Open http://HOST:8080 in a browser — Three.js modules load correctly. 2026-04-13 18:24:59 -04:00			`- "8080:8080"`
rewrite: docker-compose for WS heartbeat port only — drop 4200/3001 (#548) 2026-03-26 16:43:49 +00:00			`- "8765:8765"`
fix: align docker-compose.yml with deploy.sh services 2026-04-13 00:26:55 +00:00			`nexus-staging:`
			`build: .`
			`container_name: nexus-staging`
			`restart: unless-stopped`
			`ports:`
feat: unified HTTP+WS server for proper URL deployment Closes #1339. The Nexus Three.js app required HTTP serving for module imports to work (file:// and raw Forge URLs break). This change: - server.py: dual-purpose async server — HTTP on :8080 (static files) and WebSocket on :8765 (broadcast gateway), single process - Dockerfile: exposes both 8080 (HTTP) and 8765 (WS), includes all frontend assets (boot.js, bootstrap.mjs, gofai_worker.js, etc.) - docker-compose.yml: maps HTTP :8080/:8081 + WS :8765/:8766 - deploy.sh: updated for new port layout - run.sh: standalone no-Docker launcher - app.js: WS URL derives from HTTP port (8080->8765, 8081->8766) - deploy.yml workflow: docker compose on remote host To deploy: `./deploy.sh` (Docker) or `./run.sh` (bare metal). Open http://HOST:8080 in a browser — Three.js modules load correctly. 2026-04-13 18:24:59 -04:00			`- "8081:8080"`
			`- "8766:8765"`