How kyanowo1107/meowstatus works
MeowStatus is a personal status hub: visitors read a public dashboard, while an administrator authenticates to manage profile status, widgets, themes, copy, and local assets. Enabled widgets are periodically or manually refreshed through provider plugins; their snapshots and configuration feed the dashboard. The source excerpts show the poller/store/provider calls and selected API/UI interactions; broader admin routing and dashboard capabilities are documented in the README, so those links cite it.
Main entry points: store.py Status store · admin.js Admin console · main.py HTTP application · poller.py Widget poller
Components 20
Web experience
- Public dashboard
app/static/public.js - Admin console
app/static/admin.js - Theme renderer
app/static/theme.js
Application API
- HTTP application
app/main.py - Runtime configuration
app/config.py - Admin authentication
app/main.py - Profile and dashboard API
app/main.py - Widget management API
app/main.py - Theme and assets API
app/main.py
Widget monitoring
- Widget poller
app/poller.py - Provider registry
app/plugins/base.py - Provider contract
app/plugins/base.py - Minecraft providers
app/plugins/minecraft.py - HTTP service provider
app/plugins/service.py
Persistent settings
- Status store
app/store.py
Other components
- Visitor
- Administrator
- Minecraft servers
- Monitored services
- Local asset files
Connections 23
- Visitor → Public dashboard: views
README.md - Public dashboard → HTTP application: requests dashboard
app/static/public.js - HTTP application → Profile and dashboard API: routes reads
README.md - Administrator → Admin console: manages
README.md - Admin console → Admin authentication: authenticates
README.md - Admin console → Widget management API: manages widgets
app/static/admin.js - Admin console → Profile and dashboard API: loads dashboard
app/static/admin.js - Admin console → Theme and assets API: saves appearance
README.md - Theme renderer → Theme and assets API: loads theme
app/static/theme.js - HTTP application → Runtime configuration: loads settings
app/main.py - HTTP application → Widget poller: starts polling
app/main.py - HTTP application → Status store: uses persistence
app/main.py - Profile and dashboard API → Status store: reads status
app/main.py - Widget management API → Status store: manages records
app/main.py - Theme and assets API → Status store: persists settings
app/main.py - Widget poller → Status store: loads widgets
app/poller.py - Widget poller → Provider registry: dispatches provider
app/poller.py - Widget poller → Status store: writes snapshots
app/poller.py - Minecraft providers → Provider contract: implements
app/plugins/minecraft.py - HTTP service provider → Provider contract: implements
app/plugins/service.py - Minecraft providers → Minecraft servers: queries
README.md - HTTP service provider → Monitored services: checks endpoint
app/plugins/service.py - Theme and assets API → Local asset files: serves configured files
README.md