feat(platform): add vehicle data management console
This commit is contained in:
44
vehicle-data-platform/docs/deployment.md
Normal file
44
vehicle-data-platform/docs/deployment.md
Normal file
@@ -0,0 +1,44 @@
|
||||
# Deployment
|
||||
|
||||
## Build
|
||||
|
||||
Run from repository root:
|
||||
|
||||
```bash
|
||||
cd vehicle-data-platform
|
||||
pnpm --dir apps/web install
|
||||
pnpm run web:build
|
||||
cd apps/api
|
||||
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o ../../dist/platform-api ./cmd/platform-api
|
||||
```
|
||||
|
||||
## ECS Paths
|
||||
|
||||
```text
|
||||
/opt/lingniu-vehicle-platform/current
|
||||
/opt/lingniu-vehicle-platform/releases
|
||||
/opt/lingniu-vehicle-platform/env/platform.env
|
||||
```
|
||||
|
||||
## Environment
|
||||
|
||||
```text
|
||||
HTTP_ADDR=:20300
|
||||
STATIC_DIR=/opt/lingniu-vehicle-platform/current/web
|
||||
MYSQL_DSN=lingniu_vehicle:***@tcp(rm-bp179zbv481rnw3e2.mysql.rds.aliyuncs.com:3306)/lingniu_vehicle_data?parseTime=true&loc=Local
|
||||
REDIS_ADDR=r-bp1u741kij7e51i481.redis.rds.aliyuncs.com:6379
|
||||
REDIS_USERNAME=lingniu_vehicle
|
||||
REDIS_PASSWORD=***
|
||||
REDIS_DB=50
|
||||
TDENGINE_DSN=http://root:***@172.17.111.57:6041
|
||||
TDENGINE_DATABASE=lingniu_vehicle_ts
|
||||
CAPACITY_CHECK_BIN=/opt/lingniu-go-native/current/capacity-check
|
||||
AUTH_TOKEN=***
|
||||
```
|
||||
|
||||
## Health
|
||||
|
||||
```bash
|
||||
curl -fsS http://127.0.0.1:20300/api/ops/health
|
||||
curl -fsS 'http://127.0.0.1:20300/api/vehicles?limit=5'
|
||||
```
|
||||
24
vehicle-data-platform/docs/product-spec.md
Normal file
24
vehicle-data-platform/docs/product-spec.md
Normal file
@@ -0,0 +1,24 @@
|
||||
# Vehicle Data Platform Product Spec
|
||||
|
||||
## Visual Direction
|
||||
|
||||
The UI is a professional vehicle data operations console. It uses Semi UI as the component base, a restrained gray-white control-room palette, dense but readable tables, right-side drawers for detail, and blue-cyan accents for primary actions. It should feel closer to a cloud data console than a marketing dashboard.
|
||||
|
||||
## Primary Screens
|
||||
|
||||
1. Dashboard: KPI summary, protocol distribution, vehicle map preview, quality issues, and link health.
|
||||
2. Vehicles: table-first identity and vehicle registry.
|
||||
3. Realtime: table/map switch for current vehicle state.
|
||||
4. Vehicle Detail: identity header and tabs for latest state, history, raw, mileage, and quality.
|
||||
5. History: location and raw-frame query workspace.
|
||||
6. Mileage: daily and range mileage analysis.
|
||||
7. Quality: data quality and link health workspace.
|
||||
|
||||
## Interaction Rules
|
||||
|
||||
- Tables are the default data surface.
|
||||
- Filters stay above the table.
|
||||
- Details open in a right drawer unless a full route is needed.
|
||||
- Error and empty states must be explicit.
|
||||
- No decorative hero, no oversized marketing card layout, no dark large-screen style.
|
||||
|
||||
Reference in New Issue
Block a user