chore: rename repository to NODEDC MISSION CORE
This commit is contained in:
@@ -30,7 +30,7 @@ Rerun gRPC/proxy on TCP 9876
|
||||
+--> rerun_grpc_url in REST/WebSocket state
|
||||
|
|
||||
v
|
||||
self-hosted @rerun-io/web-viewer inside NODE.DC Control Station
|
||||
self-hosted @rerun-io/web-viewer inside Mission Core Control Station
|
||||
|
||||
React console <-- REST + WebSocket state --> FastAPI on 127.0.0.1:8000
|
||||
```
|
||||
@@ -52,7 +52,7 @@ Prerequisites are the repository-local Python environment and Node.js 20.19+ or
|
||||
|
||||
```bash
|
||||
uv sync --group dev
|
||||
cd apps/k1-viewer
|
||||
cd apps/control-station
|
||||
npm install
|
||||
npm run typecheck
|
||||
npm run build
|
||||
@@ -121,7 +121,7 @@ does not publish an application request or modeling command.
|
||||
|
||||
On the first live or replay session, `RerunBridge`:
|
||||
|
||||
- creates an explicit `RecordingStream("nodedc_device_spatial")`;
|
||||
- creates an explicit `RecordingStream("nodedc_mission_core_spatial")`;
|
||||
- installs the default spatial blueprint;
|
||||
- starts the gRPC/proxy server on TCP 9876 with a 512 MiB late-client buffer;
|
||||
- reports `rerun+http://127.0.0.1:9876/proxy` only after the server is ready;
|
||||
|
||||
Reference in New Issue
Block a user