-
Notifications
You must be signed in to change notification settings - Fork 2
Deployment and Operations Guide
GiZano edited this page Aug 5, 2026
·
2 revisions
This section outlines the procedures for provisioning the QuakeGuard infrastructure.
- Backend: Docker Engine & Docker Compose.
- Edge (IoT): VS Code + PlatformIO extension.
- Mobile: Node.js (v18+) & Expo Go app.
- Navigate to
backend/api. - Copy the environment variables:
cp .env.example .envand fill in your HiveMQ credentials. - Launch the stack:
docker compose up --build -d- Verify health at
http://localhost:8000/health. -
(Optional) To enable on-premise AI emergency reports, use the
aiprofile — see AI Emergency Report Service.
- Navigate to
firmware/esp32_code. - Copy the config:
cp esp32_config.env.example esp32_config.env. - Update WiFi credentials,
SERVER_HOST, andENROLLMENT_TOKEN. - Flash via PlatformIO.
- Open Serial Monitor (115200 baud) to verify successful automated registration.
- Navigate to
mobile/and runnpm install. - Create a
.envfile mapping your backend secrets and IP:
EXPO_PUBLIC_IOT_API_KEY=your_secret_key
EXPO_PUBLIC_MOBILE_WS_TOKEN=your_ws_token
EXPO_PUBLIC_API_BASE_URL=http://YOUR_LOCAL_IP:8000- Run
npx expo startand scan the QR code with your smartphone.
Validate your infrastructure by simulating a 150-node seismic swarm:
cd backend/api
export API_URL="http://localhost:8000"
export NUM_SENSORS=150
python -m tests.stress_testA successful run ends with 🏆 SYSTEM CERTIFIED.
- Previous: AI Emergency Report Service
- Related: Troubleshooting & Usage Guide
- Back to: Home