runwisp Files

Added

• Full-text log search across a task's runs. Press / in the TUI, or click Search in the task header (or ⌘K / Ctrl K) in the Web UI, to grep every captured run of a task for a substring or RE2 regex, case-sensitive or not. Hits are grouped by run with the run's start time as the heading; click one and the existing log viewer jumps to the line and pulses a highlight. The scan is on-demand — no background index, no extra disk usage — and walks runs newest-first in parallel, with an opaque cursor for paging through long histories. The Web UI modal pages through older runs as you scroll, so tasks with thousands of runs are searchable end-to-end. Exposed at GET /api/tasks/{name}/log/search. See Logs / Search.

• Observable Docker Compose services. Point RunWisp at an existing docker-compose.yml and every service becomes an observable RunWisp service — per-container logs streamed and indexed, restart policies enforced, notifications on failure, trigger/stop from the Web UI and REST API. Drop one line next to your compose file ([compose.myapp]) and RunWisp auto-discovers compose.yaml / docker-compose.yml and imports every service. Mix and match modes — mode = "services" (default) supervises each compose service independently, mode = "stack" runs the whole project as one unit. Per-service overrides ([compose.myapp.api]) layer RunWisp knobs onto specific services without touching the compose file. [services.*] and [tasks.*] can also point at a single compose service via compose_file + compose_service for long-running supervision or cron-driven one-shots. First-run scaffolding detects adjacent compose files and offers an opt-in starter import. See [compose.*] and the migration guide.