Docker Compose

Use this when you do not want three terminals. Docker only.

Compose still needs real Supabase keys in a root .env. The example file ships empty on purpose so a service-role JWT never lands in git.

Clone and copy env

git clone git@github.com:sachio222/porto.git && cd porto
cp .env.compose.example .env

Fill the two required keys

For a local stack, start a one-shot Supabase (or reuse keys from a previous supabase status) and paste:

Variable	Where it goes
`SUPABASE_SERVICE_ROLE_KEY`	Backend only. Full DB access. Never ship to the browser.
`SUPABASE_ANON_KEY`	Frontend build. Public, RLS-gated JWT.

Defaults for URLs are already in docker-compose.yml (http://localhost:54321, ws://localhost:8000/ws).

Start the stack

docker compose up

Ports

Service	URL	What it is
Frontend	`http://localhost:3000`	Next.js production build
Backend	`ws://localhost:8000/ws`	FastAPI + uvicorn
Kong	`http://localhost:54321`	Supabase REST / auth (`SUPABASE_URL`)
Postgres	`localhost:54322`	Direct Postgres
Studio	`http://localhost:54323`	Database admin UI

Migrations under frontend/supabase/migrations/ apply on first boot.

docker compose down        # stop
docker compose down -v     # stop and drop volumes

You want hot reload (uvicorn --reload, next dev)
You are attaching CLI harnesses that must spawn as your user (claude, grok, codex look in this $HOME)
You are pointing Local / network at a host on the same machine (Ollama on 127.0.0.1)

CLI seats and local Ollama are simpler on the from-source path. A containerized API does not inherit your desktop CLI login.