discover · compare · collections · requirements · contribute · feed · watching · stats · help with your tokens
Timmoth/RackPeek · source
Snapshot 0 · 2026-11-04T12:47:28Z · C# · AGPL-3.0
Content fingerprint
528940bc9423f23c42bbed36e6cc722c92ddbf52bb1a2537da8f86e231ada367GitHub description at capture
CLI tool to discover, manage, and document your IT infrastructure and home lab.
README at capture
[](https://timmoth.github.io/RackPeek/)   [](https://discord.gg/egXRPdesee) [](https://timmoth.github.io/RackPeek/) [](https://hub.docker.com/r/aptacode/rackpeek/) RackPeek is a self-hosted CLI and web app for documenting home labs and small IT environments. Track hardware, systems, services, and connections in a portable YAML inventory. Use the CLI or web app to manage it, discover existing infrastructure, and export data for tools such as Ansible. ## Quick start Run RackPeek with a persistent Docker volume: ```sh docker volume create rackpeek-config docker run -d \ --name rackpeek \ -p 8080:8080 \ -v rackpeek-config:/app/config \ aptacode/rackpeek:latest ``` Open [http://localhost:8080](http://localhost:8080). RackPeek stores its inventory in `config.yaml` inside the volume. For bind mounts, the host directory must be writable by container user `1654`; add `:Z` on SELinux systems. ## Mobile app The iOS and Android app supports local inventory editing and syncs with a RackPeek server when connected. The app is in early access; [join the Discord](https://discord.gg/egXRPdesee) for updates and testing information. ## Documentation - [Overview](https://timmoth.github.io/RackPeek/docs/overview) - [Installation](https://timmoth.github.io/RackPeek/docs/install-guide) - [CLI reference](https://timmoth.github.io/RackPeek/docs/cli-commands) - [Discovery](https://timmoth.github.io/RackPeek/docs/discovery-guide) - [Inventory API](https://timmoth.github.io/RackPeek/docs/inventory-api) - [MCP server](https://timmoth.github.io/RackPeek/docs/mcp-guide) - [Ansible inventory](https://timmoth.github.io/RackPeek/docs/ansible-generator-guide) ## Development See the [developer setup](docs/development/dev-setup.md), [testing guide](docs/development/testing-guidelines.md), and [contribution guide](docs/development/contribution-guidelines.md). The release process is in [release-guide.md](docs/development/release-guide.md).