bonaminandClaude Opus 5.5
6ea7e9d2c5
docs/mqtt-app-user-auth.md records what future sessions (and whoever builds the phone app) need and can't get from the code alone: - app connection contract: username app_<uid>, Firebase ID token as password, client id prefix app_<uid>_, TLS only, allowed topics per acc, - serial field (serial_number, legacy device_id) and the device_serials mirror + every code path that must keep it in sync, - the uid-field lookup rule and ACL cache invalidation, - legacy "vesper" password flag and its log line, - rollout checklist: backfill, go-auth VPS config (required/recommended), files-ACL check, TLS listener, - decisions/gaps: FlutterFlow must sync device_serials itself; the device_users subcollection is intentionally ignored. CLAUDE.md gets a short section pointing agents at it before they touch MQTT auth or anything that edits user_list/status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BellSystems Admin Panel
Self-hosted web admin panel for managing BellSystems devices, melodies, users, and MQTT communications.
Tech Stack
- Backend: Python / FastAPI
- Frontend: React + Tailwind CSS (Vite)
- Database: Google Firestore (Firebase Admin SDK)
- MQTT: Mosquitto (paho-mqtt)
- Auth: JWT with role-based access control
- Deployment: Docker Compose + Nginx
Getting Started
# Clone the repo
git clone <your-gitea-url>/bellsystems-admin.git
cd bellsystems-admin
# Copy env template and fill in your values
cp .env.example .env
# Place your Firebase service account key in the project root
# (file is gitignored — never commit it)
# Start everything
docker compose up --build
Project Structure
bellsystems-admin/
├── backend/ # FastAPI API server
├── frontend/ # React SPA
├── nginx/ # Reverse proxy config
├── docker-compose.yml
└── .env
Documentation
See BellSystems_AdminPanel_Strategy.md for the full architecture and build plan.