How virtualoptimization/vo-server works
VO-server is a FastAPI backend for an iOS LiDAR room-scanning and furniture-placement service. The implemented workflow accepts a typed scan at the versioned API, passes it to an endpoint, and returns an S3-style key; the S3 helper is currently a stub, and database persistence is explicitly TODO. The README also describes optimization, USDZ-to-FBX conversion, code-based VR lookup, and WebSocket synchronization, but their implementation files are absent from the supplied tree. Those capabilities are shown as documented, unverified subsystems, not inspected runtime components.
Main entry points: scans.py Scan receiver · router.py v1 router · s3.py S3 uploader stub · main.py FastAPI app
Components 12
Scan API
- FastAPI app
server/main.py - v1 router
server/api/v1/router.py - Scan receiver
server/api/v1/endpoints/scans.py - Scan schemas
server/schemas/scan.py
Storage configuration
- S3 uploader stub
server/core/s3.py - Settings
server/core/config.py
Documented capabilities
- Placement optimizer
- USDZ-FBX converter
- VR code lookup
- Furniture sync
Other components
- iOS scanner
- VR client
Connections 10
- iOS scanner → Scan receiver: submits scan
README.md - FastAPI app → v1 router: mounts routes
server/main.py - v1 router → Scan receiver: routes scans
server/api/v1/router.py - Scan receiver → Scan schemas: accepts payload
server/api/v1/endpoints/scans.py - Scan receiver → S3 uploader stub: calls upload
server/api/v1/endpoints/scans.py - S3 uploader stub → Settings: reads settings
server/core/s3.py - Scan receiver → Placement optimizer: optimization workflow
README.md - Placement optimizer → USDZ-FBX converter: converts model
README.md - VR client → VR code lookup: requests room
README.md - VR client → Furniture sync: interacts live
README.md