Development stack

Run the whole platform on macOS with seeded demo data.

Repository-validated operator guidance View source ↗

#Start and stop

From the repository root

./native.sh start
./native.sh status
./native.sh logs
./native.sh stop

#What starts

Postgres and Redis run as Homebrew services. Beacon runs as a launchd user agent. The API and Web run as background processes. The API seeds demo data, so you can sign in immediately.

Demo access

Demo login: admin@example.com (dev seed only — use /setup credentials in production)
API:  http://127.0.0.1:8080/api/v1
Web:  http://127.0.0.1:3000

#Where state lives

Path	Purpose
.dev-logs/	Process logs.
.dev-pids/	Background process IDs.
.dev-data/	Beacon data and workload files.
.dev-secrets.env	Generated dev secrets.

#Container limits

Docker on macOS is Colima

If Colima is stopped, Beacon runs but cannot start containers. API and UI still work against seeded Postgres data, so HTTP and UI paths remain verifiable while container lifecycle does not. The container-based equivalent is scripts/dev/start-dev.sh.