How interstella0/zegraph-web works
ZE Graph Website lets players explore Zombie Escape server activity, maps, player histories, and live radar data. The browser requests the Rust API through Next.js routes; the API serves database-backed results and exposes MCP tools. The README describes data collection as a separate, hidden scraper that populates PostgreSQL, and identifies QGIS as the source of map layers. The tree and excerpts establish the main runtime layers, but do not show every route-to-handler or worker-to-storage call, so those links are not expanded.
Main entry points: src/main.rs Rust API service · page.tsx ZE Graph site · api Next.js API routes · src/main.rs Profile picture service
Components 22
Web experience
- ZE Graph site
front-ze/app/page.tsx - Server explorer
front-ze/app/servers/[server_slug]/page.tsx - Maps and 3D
front-ze/app/servers/[server_slug]/maps/[map_name]/page.tsx - Player profiles
front-ze/app/servers/[server_slug]/players/[player_id]/page.tsx - Radar and tracker
front-ze/app/servers/[server_slug]/radar/page.tsx - Next.js API routes
front-ze/app/api
API and services
- Rust API service
src/main.rs - Domain routers
src/routers.rs - MCP tools
src/mcp/mod.rs - Push notifications
src/core/push_service.rs
Data platform
- Data workers
src/workers/mod.rs - PostgreSQL
- Redis cache
- Map and model storage
src/core/storage.rs
External integrations
- QGIS Server
- Profile picture service
pfp-provider/src/main.rs - Profile providers
pfp-provider/src/providers.rs
Other components
- Website user
- Hidden data scraper
- Steam API
- External profile sources
- S3-compatible storage
Connections 27
- Website user → ZE Graph site: browses
- ZE Graph site → Server explorer: opens
- ZE Graph site → Maps and 3D: opens
- ZE Graph site → Player profiles: opens
- ZE Graph site → Radar and tracker: opens
- Server explorer → Next.js API routes: requests data
- Maps and 3D → Next.js API routes: requests data
- Player profiles → Next.js API routes: requests data
- Radar and tracker → Next.js API routes: requests data
- Next.js API routes → Rust API service: proxies requests
- Rust API service → Domain routers: dispatches
- Domain routers → PostgreSQL: queries and writes
- Rust API service → MCP tools: mounts endpoint
- Data workers → PostgreSQL: writes data
- Hidden data scraper → PostgreSQL: populates
- PostgreSQL → Hidden data scraper: supplies data
- PostgreSQL → QGIS Server: PostGIS data
- QGIS Server → Radar and tracker: serves WMS layers
- Rust API service → Profile picture service: requests profile images
- Profile picture service → Profile providers: tries providers
- Profile providers → Steam API: queries
- Profile providers → External profile sources: queries
- Rust API service → Push notifications: uses service
- Rust API service → Map and model storage: stores map and model files
- Map and model storage → S3-compatible storage: stores objects
- Rust API service → Redis cache: uses cache
- Profile picture service → Redis cache: caches lookups