Verify and Maintain

Check Service Health

bun run stack ps

Verify infrastructure, migrations, backend, frontend, chat, and worker services. A completed migration container is expected; a required long-running service repeatedly restarting is not.

Check the backend directly:

curl http://127.0.0.1:3000/health

The local machine-readable API schema is available at http://127.0.0.1:3000/docs/spec.json, and the backend-hosted API explorer is at http://127.0.0.1:3000/docs.

Read Logs

bun run stack logs -f

Use service-specific Compose filtering when one process is failing. Healthy scheduler and recovery polls are intentionally quiet; focus on startup, shutdown, failures, and recovery events.

Stop and Restart

bun run stack down
bun run stack up

Persistent mode preserves named volumes. Disposable mode intentionally removes local state as part of its lifecycle.

Update the Repository

After pulling changes:

bun install
bun run stack env
bun run stack config
bun run stack up

Rebuilds are required when Dockerfiles, pinned binaries, package dependencies, or image-owned integration launchers change.

Verify Source Changes

bun run check
bun test

check covers the product workspace. Contributors changing the public sites should also run bun run sites:check; bun run check:all runs both dependency roots.

Reset Local Data

bun run stack reset --confirm

Troubleshooting Order

1. Run bun run stack config to catch invalid configuration.
2. Run bun run stack ps to find the failing service.
3. Read that service’s logs.
4. Check port conflicts and authentication inputs.
5. Reset only when losing local data is acceptable and state corruption is the actual problem.

For symptom-based help, see Troubleshooting.