Yicong-Huang opened a new issue, #5960: URL: https://github.com/apache/texera/issues/5960
### Feature Summary Spinning up the local dev stack today means juggling several terminals: docker compose for infra, `sbt dist` plus six launcher scripts for the JVM services, `cd agent-service && bun run dev`, `cd frontend && yarn start`. Bouncing one service after a code change means tracking down the right terminal. There's no single view of "is everything up, what's dirty, what's running stale code." ### Proposed Solution Add a self-contained dev stack manager under `bin/`. **`bin/local-dev.sh`** — single shell script that knows the whole steady-state workflow: - `up` / `down`: bring the entire stack up or down (5 infra docker containers + 6 JVM services + agent-service + frontend) - `start <svc>` / `stop <svc>` / `<svc>`: per-service ops (the bare form rebuilds + bounces one JVM) - `status` / `logs <svc>` - Skips `sbt dist` when nothing changed (per-service content-hash check, robust to `git checkout` moving mtimes) - Pre-bounces running JVMs before `unzip -o` so overlapping unzips don't corrupt live class loading **`bin/local-dev-tui.py`** — matching Textual dashboard: - Live service table (state, port, PID, artifact mtime, BUILD indicator) - Log pane hidden by default; auto-shown for running commands and on failures - Double-click a row (or Enter) → tail that service's log - ↑/↓ command history, persisted across sessions - ESC exits log view; Ctrl-C cancels active command, second press exits ### Scope - macOS only for the first cut (uses `stat -f`, BSD `lsof`). Linux portability deferred to a follow-up issue. - Tooling only — no app behaviour change, no impact on CI. ### Acceptance `bin/local-dev.sh` (no args) launches the TUI; CLI subcommands work standalone for scripting. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
