The core of the second generation of UMA Companion.
Used in UMA Companion
Trace it on the map →Stack
What I’ve used, and where
Every tool here was used in a real project or runs in the lab. Nothing is rated, because a list of skills means little next to the thing it built. Follow a tool to see which.
Languages and frameworks
The TSX interface on top of the Rust core.
Used in UMA Companion
Trace it on the map →The first prototype and the PySide6 desktop app.
Used in UMA Companion
Qt 6 desktop interface and the custom AETHER design system.
Used in UMA Companion
The first prototype interface, outgrown for rendering and drag-and-drop.
Used in UMA Companion
The web platform’s frontend, alongside React.
Used in UMA Companion
The web platform’s backend, with SQLAlchemy and Alembic.
Used in UMA Companion
Data and automation
Local-first state, with catalogue and user tables kept apart.
Used in UMA Companion
Trace it on the map →Scraping, moved to maintainer-run jobs rather than shipped to users.
Used in UMA Companion
Trace it on the map →Runs the scrapers and publishes the catalogue data packs.
Used in UMA Companion
Trace it on the map →Virtualisation and storage
The main compute host, running VMs and LXC containers.
Used in The homelab, made understandable, Media, with fewer boundaries
Trace it on the map →The OS of the media VM that now owns the storage.
Used in Media, with fewer boundaries, The homelab, made understandable
Trace it on the map →Storage pools, now local to the VM that uses them.
Used in Media, with fewer boundaries
Trace it on the map →Lightweight containers on Proxmox; Pi-hole used to live in one.
Used in The homelab, made understandable, A separate home for DNS
How most small services run, including Jellyfin.
Used in The homelab, made understandable, Media, with fewer boundaries, A separate home for DNS
Trace it on the map →The management view over the containers.
Used in The homelab, made understandable
Trace it on the map →The storage VM that came before; kept powered off as a rollback.
Used in Media, with fewer boundaries
Network and access
Answers and filters DNS for the network, now on the Pi.
Used in A separate home for DNS, The homelab, made understandable
Trace it on the map →Recursive resolver behind Pi-hole.
Used in A separate home for DNS, The homelab, made understandable
Trace it on the map →Private remote access, so no router port is needed.
Used in The homelab, made understandable
Trace it on the map →Carries public traffic to the lab over an outbound connection.
Used in The homelab, made understandable, This website, Media, with fewer boundaries
Trace it on the map →Serves this site’s static files.
Used in The homelab, made understandable, This website
Trace it on the map →Services and monitoring
Media server reading local ZFS datasets.
Used in Media, with fewer boundaries
Trace it on the map →Trialled beside Plex with read-only media mounts.
Used in Media, with fewer boundaries
Trace it on the map →Hub-and-agent host metrics, lighter than Grafana and Prometheus.
Used in A separate home for DNS, The homelab, made understandable
Trace it on the map →Availability monitoring.
Used in The homelab, made understandable
Trace it on the map →Websites
Builds this site ahead of time into plain static files.
Used in This website
Trace it on the map →Built the previous version of the site, and its recovered baseline.
Used in This website