External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: reflow hard-wrapped prose to one line per paragraph

Browse Source 
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.
This commit is contained in:
Renn F
2026-06-16 23:18:55 +02:00
parent 640a964b88
commit f48106cbb6
67 changed files with 504 additions and 1593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
panel/README.md
+5 -17
View File
@@ -1,9 +1,6 @@
# 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.
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
@@ -23,16 +20,12 @@ Use the root-level Docker Compose:
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:
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`.
The panel uses relative URLs (`/api/v1`, `/ws`) so nothing here needs a backend URL in `.env`.
## Running the panel alone for UI development
@@ -42,10 +35,7 @@ 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.
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
@@ -64,6 +54,4 @@ then run `pnpm dev` against that.
## 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.
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.