mrdaemon / exosphere

Exosphere Exosphere is a CLI and Text UI driven application that offers aggregated patch and security update reporting as well as basic system status across multiple Unix-like hosts over SSH. It is targeted at small to medium sized networks, and is designed to be simple to deploy and use, requiring no central server, agents and complex dependencies on remote hosts. If you have SSH access to the hosts and your keypairs are loaded in a SSH Agent, you are good to go! Simply follow the Quickstart Guide, or see the documentation to get started. Key Features • Rich interactive command line interface (CLI) • Text-based User Interface (TUI), offering menus, tables and dashboards • Consistent view of information across different platforms and package managers • See everything in one spot, at a glance, without complex automation or enterprise solutions • Does not require Python (or anything else) to be installed on remote systems • Parallel operations across hosts with optional SSH pipelining • Document based reporting in HTML, text or markdown format • JSON output for integration with other tools Compatibility Exosphere itself is written in Python and is compatible with Python 3.13 or later. It can run nearly anywhere where Python is available, including Linux, MacOS, and Windows (natively). Supported platforms for remote hosts include: • Debian/Ubuntu and derivatives (using APT) • Red Hat/CentOS and derivatives (using YUM/DNF) • FreeBSD (using pkg) • OpenBSD (using pkg_add) Unsupported platforms with SSH connectivity checks only: • Other Linux distributions (e.g., Arch Linux, Gentoo, NixOS, etc.) • Other BSD systems (NetBSD) • Other Unix-like systems (e.g., Solaris, AIX, IRIX, Mac OS) Exosphere **does not support** other platforms where SSH is available. This includes network equipment with proprietary operating systems, etc. Documentation For installation instructions, configuration and usage examples, full documentation is available. Development Development Quick Start TL;DR, use uv Linting, formatting and testing can be done with poe tasks: For more details, and available tasks, run: UI Development Quick Start The UI is built with Textual. A quick start for running the UI with live editing and reloading, plus debug console, is as follows: Congratulations! Editing any of the files in the directory will reflect changes immediately. Make sure you run Exosphere UI with . Documentation Editing Quick Start To edit the documentation, you can use the following commands: This will start a local server at where you can view the documentation. You can edit the files in the directory, and the changes will be reflected in real-time. To check the documentation for spelling errors, you can run: Linting is performed as part of the task, which also builds the documentation, but can also be invoked separately: Project Structure The project is managed via uv and , which contains all dependencies, scripts, and metadata for the application. Exosphere uses Poe the Poet as a task runner, and all tasks are defined in the file under the table. Root Directory | path | description | | ---- | ----------- | | | Sphinx documentation source tree | | | Custom Sphinx extensions for the project | | | Example configuration files and reports | | | Utilitarian scripts for dev and maintenance | | | Main source code for the application | | | Test suite for the application | Source Tree | path | description | | ---- | ----------- | | | Main application source code | | | CLI command implementations | | | Package Manager Provider implementations (e.g. debian, freebsd, redhat, etc) | | | Reporting JSON schema definitions | | | Discovery and platform detection module | | | Jinja2 templates for reporting | | | Textual UI source code | | | Textual CSS for styling the UI | The rest of the source tree should be fairly self-explanatory. Core Modules Paths below are relative to unless otherwise noted. | module | description | | ------ | ----------- | | | Main entry point for the application | | | Package manager provider API and base classes | | | Concrete provider factory for creation of Package Managers | | | CLI interface entry point | | | Configuration subsystem, including defaults | | | Context management for shared state across commands and UI | | | Data models and structures for serialization and exchange | | | Cache system for serialization | | | Exception classes and general error messages | | | Inventory management subsystem | | | Cache format migration processes | | | Main objects for representing Hosts, and most of the relevant logic | | | SSH pipelining implementation, including reaper thread | | | REPL module for interactive CLI usage | | | Reporting subsystem, including templates and formatters | | | Sudo management subsystem, including policy and utilities | Generally, most of the things Exosphere does to hosts (including connection management and operations) are going to be found in . UI Modules Paths below are relative to unless otherwise noted. | module | description | | ------ | ----------- | | | Main Textual application class and entry point for the UI | | | UI Context management for shared state across UI components | | | Shared UI elements, including task runners | | | Dashboard view implementation | | | Inventory view implementation | | | Logs view implementation | | | Screen refresh and message passing system | The TCSS for all of it is in a single file under . Using Exosphere as a Library This use case is not currently well supported, but it is possible to use Exosphere as a library. The documentation for this (alongside actual examples) is still a WIP, but you can refer to the Online API Documentation for the core functionality and objects that are considered public. License This project is licensed under the MIT License - see the LICENSE file for details.