mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
Renn F
f48106cbb6
Markdown and editors soft-wrap on their own, so the manual ~75-char line breaks across the docs added nothing but noise. Join wrapped prose, list items, and paragraphs into single lines across 67 docs — README, CLAUDE.md, deployment, usage, the RAG knowledge base, and the agent role prompts. Whitespace-only: code fences, tables, and blockquote alerts are byte-identical and the change is token-verified (no content altered). Applied with a deterministic reflow tool (committed separately). Also lands two doc edits that were awaiting commit: the measured under-load resource numbers in usage.md and the pr_reviewer additions to the org-structure RAG doc.
58 lines
2.1 KiB
Markdown
58 lines
2.1 KiB
Markdown
# RoboCo Control Panel
|
|
|
|
Next.js 16 control panel for the RoboCo AI agent system. Formerly a separate repository (`rennf93/roboco-panel`), now vendored under `panel/` in this monorepo so `docker compose up -d` brings up the whole stack from one place.
|
|
|
|
## Stack
|
|
|
|
- Next.js 16 (App Router, standalone output)
|
|
- TypeScript
|
|
- Tailwind CSS
|
|
- Radix UI primitives
|
|
- `dnd-kit` for drag/drop (kanban)
|
|
- pnpm for package management
|
|
|
|
## Running in production (the normal path)
|
|
|
|
Use the root-level Docker Compose:
|
|
|
|
```bash
|
|
# from the repo root (one level up from this directory)
|
|
docker compose up -d
|
|
```
|
|
|
|
The panel is built as part of the compose stack via `docker/panel.Dockerfile` and served internally on port 3000. Nginx (also in the compose stack) is the single externally-exposed service on `http://localhost:3000` and routes:
|
|
|
|
- `/api/*` and `/ws/*` → orchestrator (FastAPI, port 8000)
|
|
- everything else → the Next.js panel
|
|
|
|
The panel uses relative URLs (`/api/v1`, `/ws`) so nothing here needs a backend URL in `.env`.
|
|
|
|
## Running the panel alone for UI development
|
|
|
|
```bash
|
|
cd panel
|
|
pnpm install
|
|
pnpm dev
|
|
```
|
|
|
|
That gives you Next dev-server on `localhost:3000`, but you still need the orchestrator reachable at `localhost:8000` (or via nginx) for API calls to work. Easiest: `docker compose up -d` the backend services, then run `pnpm dev` against that.
|
|
|
|
## Build scripts
|
|
|
|
- `pnpm dev` — development server with hot reload
|
|
- `pnpm build` — production build (outputs `.next/standalone/`)
|
|
- `pnpm start` — run the standalone build
|
|
- `pnpm lint` — ESLint
|
|
|
|
## Where things live
|
|
|
|
- `src/app/` — Next.js App Router pages
|
|
- `src/components/` — React components (organized by feature: tasks, agents, channels, …)
|
|
- `src/lib/api/` — typed API client (thin wrappers over `fetch`)
|
|
- `src/lib/` — constants, utilities, WebSocket hooks
|
|
- `src/types/` — shared TypeScript types mirroring backend schemas
|
|
|
|
## Backend schema changes
|
|
|
|
When the backend changes response shapes, mirror them in `src/types/` and the relevant `src/lib/api/` module. Keep API paths relative so nginx routing keeps working.
|