Internal metaserver for my homelab. It's going to be a while before it's generally usable by anyone else, so the docs are going to be thin for the near foreseeable future, and stuff will be ugly, broken, or both.
The entire theme is scope creep, so Hazel is designed for a lot of random shit I need, but don't feel like making an entire dedicated project for. Some planned ideas include:
- The obligatory link dashboard
- Status monitoring
- The obligatory real-time (ish) overview
- Practical monitoring of stuff like miniflux unreads
- System information
- Service information
- Long-running job tracking (with NTFY integration for failure or completion)
- The obligatory real-time (ish) overview
- Automation with scripting for easier expansion
The overall goal of the project is primarily to join together other self-hosted services, and to implement a few things from scratch. But for the most part, where possible, main functionality is deferred to other (primarily self-hosted) services, with Hazel serving as an aggregator.
- A Linux-based server
- C++20 compiler
- CMake 3.28 (Pro tip: CMake is available via pip)
- uuid-dev, libasio-dev (Debian-based names; look up your distro's package manager for the applicable packages). Additional dependencies are sourced automagically during the build process
Docker is not supported, because it's annoying to work with and in this case, there's absolutely 0 advantages to supporting it.