pyobs-web-admin
This is a web-based administration interface for pyobs
(documentation), the robotic telescope framework. Unlike most
pyobs_* packages, it is not itself a pyobs module loaded via a YAML class: entry –
it is a standalone Django application that manages a
fleet of pyobs module processes from the outside, via subprocess and the filesystem. It
has no import-time dependency on pyobs-core.
From a browser it lets you start, stop, and restart modules, tail and filter their logs, view and edit their YAML configuration files, audit and edit their access-control policy fleet-wide, and – optionally – manage the XMPP accounts they connect to ejabberd with.
Feature overview
Dashboard – sortable list of every module with status, RAM, CPU, uptime, and recent warning/error log counts; quick start/restart/stop/activate/deactivate per module plus bulk Start All / Restart All / Stop All. See Dashboard and module detail.
Module detail – Overview, Logs, Config, and ACL tabs for a single module. See Dashboard and module detail and ACL matrix and per-module ACL editing.
Module lifecycle – how start/stop/restart/status/logs actually work under the hood, new-module creation, shared config fragments. See How modules are managed.
ACL matrix – a fleet-wide view of every module’s access-control policy, editable in place. See ACL matrix and per-module ACL editing.
journald-backed logging – an alternative to flat log files for modules run under systemd. See journald-backed logging.
Hub mode – control multiple remote pyobs hosts from a single browser tab. See Hub mode.
ejabberd / XMPP integration (optional) – live connection status and, if wanted, account management for modules’ XMPP identities. See ejabberd / XMPP integration.
Overview page and fleet-wide Users page – cross-host summaries built on top of hub mode. See Dashboard and module detail and XMPP user management.
Getting started
Getting started
Features
Project
API reference