Skip to main content

Environments and Configuration

Deployment Environments

Local Development Port Map

Source: equa-start-dev skill, verified against package.json scripts and service configs.
Port 3000 is reserved for equa-server. The command-center-so npm run dev script binds to port 3001 (next dev -p 3001). The equa-patternlib npm run dev script binds to port 3333 (next dev -p 3333). Equa Docs binds to port 3337 to avoid that patternlib conflict. Never run other services on port 3000.

Backend Environment Variables

Source: equa-server/modules/api/src/server.ts, equa-server/modules/persistence/src/site/connecting.ts, equa-server/modules/auth/src/

Database

Server

Authentication

Email / Notifications

File Storage

Integrations

Frontend Environment Variables

Source: equa-web/webpack.config.js (DefinePlugin)
The production browser build does not hardcode a Cloud Run hostname. API_URL defaults to /api/v1, and the committed nginx config proxies /api/ to the Railway-hosted backend target.

Comet-Bridge Environment Variables

Source: Comet-Bridge/comet-mcp/src/index.ts, Comet-Bridge/scripts/lifecycle-sync.mjs See Comet Browser — Environment overrides for the full Comet-Bridge variable list.