Quick Start

Prerequisites

Bun 1.2+
Docker and Docker Compose
Pulumi CLI (v3.x)

Start the Dev Environment

git clone https://github.com/procella-dev/procella.git
cd procella
bun run dev

This starts the following services:

Service	Purpose	Port
PostgreSQL 17	Database	5432
MinIO	S3-compatible blob storage	9000 (API), 9001 (console)
Procella server	Bun server with hot-reload	9090
Vite dev server	React UI with HMR	5173

The server runs database migrations automatically on startup.

Log In with the Pulumi CLI

export PULUMI_ACCESS_TOKEN=devtoken123
pulumi login http://localhost:9090

The dev environment uses a static token (devtoken123) for authentication. This maps to the default dev user (dev-user) in the default organization (dev-org).

Create and Deploy a Stack

# Create a new Pulumi project
mkdir my-infra && cd my-infra
pulumi new typescript --yes

# Deploy
pulumi up --yes

# View the stack
pulumi stack

# Export state
pulumi stack export

# Clean up
pulumi destroy --yes
pulumi stack rm --yes

Verify the Setup

You can verify the server is running correctly:

# Health check
curl http://localhost:9090/healthz

# Check capabilities
curl -H "Accept: application/vnd.pulumi+8" http://localhost:9090/api/capabilities

# List stacks (requires auth)
curl -H "Accept: application/vnd.pulumi+8" \
     -H "Authorization: token devtoken123" \
     http://localhost:9090/api/user/stacks

Multi-Tenant Testing

The dev environment supports multiple users and organizations out of the box:

User	Token	Organization	Role
`dev-user`	`devtoken123`	`dev-org`	admin
`user-b`	`token-user-b`	`org-b`	admin
`viewer-user`	`token-viewer`	`dev-org`	viewer

# Log in as user-b
export PULUMI_ACCESS_TOKEN=token-user-b
pulumi login http://localhost:9090

# Stacks are isolated per organization — user-b can only see org-b stacks
pulumi stack ls

Stop the Environment

bun run dev:down

This stops all containers and removes volumes (including database data).

Next Steps

Configuration — customize the server with environment variables
Docker Compose — understand the deployment profiles
Testing — run the E2E acceptance test suite