Docker Deployment

Infra0 is packaged as a Docker image and is deployed using Docker Compose.

• Docker Engine 20.x or later
• Docker Compose v2.x or later
• PostgreSQL 14+ (provided by Docker Compose)
• Docker socket access (required for VS Container management)

1. 1

   infra0-app: The Next.js application container
2. 2

   postgres: The PostgreSQL database container

Create a .env file in the project root with:

# Database DATABASE_URL=postgresql://user:password@postgres:5432/infra0 DATABASE_SSL=false DATABASE_POOL_SIZE=10

# Authentication (Better-Auth) BETTER_AUTH_SECRET=your-secret-key BETTER_AUTH_URL=http://localhost:3000

# OAuth Providers (configure the ones you want to use) MICROSOFT_CLIENT_ID=your-azure-app-client-id MICROSOFT_CLIENT_SECRET=your-azure-app-secret GOOGLE_CLIENT_ID=your-google-client-id GOOGLE_CLIENT_SECRET=your-google-client-secret GITHUB_CLIENT_ID=your-github-client-id GITHUB_CLIENT_SECRET=your-github-client-secret

# AI Providers (configure the ones you want to use) ANTHROPIC_API_KEY=your-anthropic-api-key OPENAI_API_KEY=your-openai-api-key AZURE_OPENAI_API_KEY=your-azure-openai-key AZURE_OPENAI_ENDPOINT=https://your-resource.openai.azure.com GOOGLE_AI_API_KEY=your-google-ai-key OLLAMA_BASE_URL=http://localhost:11434

# Container Service (Docker socket) DOCKER_SOCKET_PATH=/var/run/docker.sock

# Feature Flags NEXT_PUBLIC_TICKETS_ENABLED=true NEXT_PUBLIC_APP_CREDENTIALS_ENABLED=true NEXT_PUBLIC_CREDENTIAL_TYPES_ENABLED=false NEXT_PUBLIC_CLOUD_PROVIDER_CREDENTIALS_ENABLED=true

1. 1

   Clone the repository
2. 2

   Create and configure the .env file
3. 3

   Run: docker compose up -d
4. 4

   Wait for both containers to start
5. 5

   Run database migrations: docker compose exec infra0-app npm run db:migrate
6. 6

   Seed initial data: docker compose exec infra0-app npm run db:seed
7. 7

   Access the application at http://localhost:3000

• The application container mounts the Docker socket (/var/run/docker.sock)
• This allows Infra0 to create and manage VS Containers for workspaces
• Ensure the Docker socket is accessible and the container runs with appropriate permissions

• docker compose down (stops and removes containers)
• docker compose down -v (also removes the database volume — WARNING: data loss)

• Database is accessible and migrations have run
• At least one OAuth provider or email auth is configured
• AI provider API key is configured
• Docker socket is mounted and accessible
• An Admin user account exists