sync: update from private repo (2ef0fa6)

2026-06-17 05:23:28 +00:00
parent 517142c61d
commit 1602d52510
42 changed files with 3387 additions and 64 deletions
@@ -97,13 +97,28 @@ first. The upgrade script detects this and offers to set it for you.
 ## 5. Launch with Docker

 ```bash
-cp .env.example .env          # set OLLAMA_BASE_URL / OLLAMA_MODEL
 docker compose up -d
 # http://localhost:9876
 ```

 The DB and workspaces are persisted in named volumes (`maestro-data` / `maestro-workspaces`). By default Compose exposes only `127.0.0.1:9876`. If you want to mount `config.yaml` from the host, see the comments in `docker-compose.yml`.

+### Browser setup wizard (no `config.yaml` editing)
+
+When you start with no LLM configured, opening the UI shows a **full-screen setup wizard** instead of the app — the browser equivalent of `npm run setup`. It walks you through:
+
+1. **Language model** — connection type, endpoint, a live connection test, then pick a model. Applied immediately, no restart.
+2. **Server port** (optional) — takes effect after a restart.
+3. **Sign-in** (optional) — email + password (first admin) or Google/Gitea OAuth. Takes effect after a restart.
+
+Because the wizard can bootstrap an admin account, mutating setup calls require a **one-time setup token**. It is printed to the server logs at startup — read it with:
+
+```bash
+docker compose logs | grep "setup token"
+```
+
+Paste that token into the wizard's first field. The token only exists during the initial no-auth window and stops working once an LLM is configured (or once auth is enabled and the server restarts). If you'd rather configure non-interactively, set `OLLAMA_BASE_URL` / `OLLAMA_MODEL` in a `.env` file (`cp .env.example .env`) before `docker compose up` — the wizard then doesn't appear.
+
 ## 6. Your first task

 1. Open the UI and create a new task (enter a title + the request body).