Self-hosting CrewForm
CrewForm needs a complete Supabase backend: PostgreSQL, Auth, REST, Realtime, Storage and Edge Functions. The application Compose file runs the frontend and task runner; it does not turn plain PostgreSQL into Supabase.Local evaluation with Docker and Supabase CLI
Install Node.js 20+, Docker and the Supabase CLI. Start Docker, then run from the repository root:http://localhost:3000 and register a local account. Email confirmations are disabled for this local evaluation configuration. Studio is at http://localhost:56323; the backend API is at http://localhost:56321. These separate ports avoid Supabase’s default ports.
Serve Edge Functions in another terminal:
002. A banned system identity with no password provides ownership for the historical marketplace seed; it cannot sign in. The bootstrap leaves supabase/.temp and linked production state alone. Configuration and secrets live in the ignored .crewform-local/ directory with restricted file permissions. Re-running environment generation preserves your encryption and webhook secrets.
To run the application directly on the host instead of Compose:
docker compose --env-file .crewform-local/app.env stop task-runner.
Stop local services without deleting data:
supabase db reset --workdir .crewform-local destroys and recreates local data. Do not run a reset against a linked or production database.
Production
Use a complete self-hosted Supabase stack or a managed Supabase project. Apply migrations with your existing migration/deployment process, deploy CrewForm’s Edge Functions, and configure the same encryption and webhook secrets on the functions and runner. Review each migration and back up an existing database before applying changes. The local bootstrap above is for evaluation; it is not a production deployment manager. Copy.env.example to an untracked .env, then set:
VITE_SUPABASE_URL: browser-accessible HTTPS backend URL.SUPABASE_INTERNAL_URL: URL reachable from the runner container. Docker’slocalhostis the container; for a backend on the host usehost.docker.internal.VITE_SUPABASE_ANON_KEYandSUPABASE_SERVICE_ROLE_KEY: public and trusted server keys respectively.API_KEY_ENCRYPTION_KEY: the same 32-byte hex AES key used by Edge Functions.WEBHOOK_SECRET: the same secret used by inbound database webhooks.VITE_APP_URLandVITE_TASK_RUNNER_URL: externally reachable application and runner URLs.
public.deployment_policy.hosted=false using an administrator database connection; browser edition flags do not change this server policy.

