[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-75152":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":13,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":16,"starSnapshotCount":16,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},75152,"RackPeek","Timmoth\u002FRackPeek","Timmoth","CLI tool to discover, manage, and document your IT infrastructure and home lab.","http:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002F",null,"C#",1571,70,8,47,0,3,14,9,73.55,"GNU Affero General Public License v3.0",false,"main",true,[26,27,28,29,30,31],"cli","home-lab","infrastructure","inventory","networking","self-hosted","2026-06-12 04:01:18","[![RackPeek demo](.\u002Fassets\u002Frackpeek_banner_thin.png)](.\u002Fassets\u002Frackpeek_banner_thin.png)\n\n![Version](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVersion-1.4.0-2ea44f) ![Status](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FStatus-Stable-success)\n[![Join our Discord](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDiscord-Join%20Us-7289DA?logo=discord&logoColor=white)](https:\u002F\u002Fdiscord.gg\u002FegXRPdesee) [![Live Demo](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLive%20Demo-Try%20RackPeek%20Online-2ea44f?logo=githubpages&logoColor=white)](https:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002F) [![Docker Hub](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDocker%20Hub-rackpeek-2496ED?logo=docker&logoColor=white)](https:\u002F\u002Fhub.docker.com\u002Fr\u002Faptacode\u002Frackpeek\u002F)\n\nRackPeek is a webui & CLI tool for documenting and managing home lab and small-scale IT infrastructure.\n\nIt helps you track hardware, services, networks, and their relationships in a clear, scriptable, and reusable way without enterprise bloat or proprietary lock-in or drowning in unnecessary metadata or process.\n\n### The roadmap for the next wave of features is actively being discussed, please make your voice heard! \n\n[![DB Tech — Finally Document Your Home Lab the Easy Way (Docker Install)](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDB%20Tech%20[video]-Finally%20Document%20Your%20Home%20Lab%20the%20Easy%20Way-blue?style=for-the-badge)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=RJtMO8kIsqU)\n[![Brandon Lee — I’m Documenting My Entire Home Lab as Code \\[video\\]](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FBrandon%20Lee%20\\[video\\]-I%E2%80%99m%20Documenting%20My%20Entire%20Home%20Lab%20as%20Code-blue?style=for-the-badge)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=wY1DgT3GD6U)\n[![Brandon Lee — I’m Documenting My Entire Home Lab](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FBrandon%20Lee%20[article]-I%E2%80%99m%20Documenting%20My%20Entire%20Home%20Lab%20as%20Code-blue?style=for-the-badge)](https:\u002F\u002Fwww.virtualizationhowto.com\u002F2026\u002F02\u002Fim-documenting-my-entire-home-lab-as-code-with-rackpeek\u002F)\n[![Jared Heinrichs — How to Document Your Entire Homelab](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FJared%20Heinrichs%20[article]-How%20to%20Document%20Your%20Entire%20Homelab-blue?style=for-the-badge)](https:\u002F\u002Fjaredheinrichs.substack.com\u002Fp\u002Fhow-to-document-your-entire-homelab)\n\n\n[![RackPeek demo](.\u002Fvhs\u002Frpk-demo.gif)](.\u002Frpk-demo.gif)\n[![RackPeek demo](.\u002Fvhs\u002Fwebui_screenshots\u002Foutput.gif)](.\u002Frpk-webui-demo.gif)\n\n## Running RackPeek with Docker\n```text\n# Named volume\ndocker volume create rackpeek-config\ndocker run -d \\\n  --name rackpeek \\\n  -p 8080:8080 \\\n  -v rackpeek-config:\u002Fapp\u002Fconfig \\\n  aptacode\u002Frackpeek:latest\n\n# Bind mount\ndocker run -d \\\n  --name rackpeek \\\n  -p 8080:8080 \\\n  -v $(pwd)\u002Fconfig:\u002Fapp\u002Fconfig \\\n  aptacode\u002Frackpeek:latest\n\n# Note - RackPeek stores its state in YAML\nconfig\u002F\n└── config.yaml\n```\nOr Docker compose\n```yaml\nversion: \"3.9\"\n\nservices:\n  rackpeek:\n    image: aptacode\u002Frackpeek:latest\n    container_name: rackpeek\n    ports:\n      - \"8080:8080\"\n    volumes:\n      - rackpeek-config:\u002Fapp\u002Fconfig\n    restart: unless-stopped\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-fsS\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 30s\n      timeout: 5s\n      start_period: 15s\n      retries: 3\n\nvolumes:\n  rackpeek-config:\n\n```\n\n## Docs\n\n* \n  [**Overview**](https:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002Fdocs\u002Foverview)\n\n* \n  [**Installation Guide**](https:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002Fdocs\u002Finstall-guide)\n\n* \n  [**Ansible Inventory Generator Guide**](https:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002Fdocs\u002Fansible-generator-guide)\n\n* \n  [**CLI Commands Reference**](https:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002Fdocs\u002Fcli-commands)\n\n* \n  [**Versioning**](https:\u002F\u002Ftimmoth.github.io\u002FRackPeek\u002Fdocs\u002Fversioning)\n\n\n## Questionnaire\n\nWe’re gathering feedback from homelabbers to validate direction and prioritize features.  \nAnswer whichever questions stand out to you, your input directly shapes the project.\n\n[![User Questionnaire](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FQuestionnaire-Share%20Feedback-orange?logo=googleforms&logoColor=white)](https:\u002F\u002Fforms.gle\u002FKKA4bqfGAeRYvGxT6)\n\n## Core Values\n\n**Simplicity**  \nRackPeek focuses on clarity and usefulness. Its scope is intentionally kept narrow to avoid unnecessary abstraction and feature creep.\n\n**Ease of Deployment**  \nThe tool exists to reduce operational complexity. Installation, upgrades, and day-to-day usage should be straightforward and low-friction.\n\n**Openness**  \nRackPeek uses open, non-proprietary data formats. You fully own your data and should be free to easily inspect, migrate, or reuse it however you choose.\n\n**Community**  \nContributors of all experience levels are welcome. Knowledge sharing, mentorship, and collaboration are core to the project’s culture.\n\n**Privacy & Security**  \nNo telemetry, no ads, no tracking, and no artificial restrictions. What runs on your infrastructure stays on your infrastructure.\n\n**Dogfooding**  \nRackPeek is built to solve real problems we actively have. If a feature isn’t useful in practice, it doesn’t belong.\n\n**Opinionated**  \nThe project is optimized for home labs and self-hosted environments, not enterprise CMDBs or corporate documentation workflows.\n\n\n## Development Docs\n\n* [`contribution-guidelines.md`](docs\u002Fdevelopment\u002Fcontribution-guidelines.md) – How to propose changes and submit PRs\n* [`dev-cheat-sheet.md`](docs\u002Fdevelopment\u002Fdev-cheat-sheet.md) – Build, release, Docker, and testing commands\n* [`testing-guidelines.md`](docs\u002Fdevelopment\u002Ftesting-guidelines.md) – Testing principles and standards\n","RackPeek 是一个用于发现、管理和记录家庭实验室及小型IT基础设施的CLI和WebUI工具。其核心功能包括硬件、服务和网络关系的追踪，以简洁、可脚本化且可复用的方式呈现，避免了企业级软件的臃肿和专有锁定。该工具采用C#开发，支持Docker部署，使得用户能够轻松地在本地或云端运行。RackPeek特别适合需要高效管理个人或小型团队IT资产的场景，如家庭实验室爱好者、小型企业和教育机构等，帮助他们维护清晰有序的技术文档库。",2,"2026-06-11 03:52:30","high_star"]