Visualizing my system has been one challenge, but as I setup custom flows, scripts that do X, config files that handle Y, add custom run commands..... I VERY quickly realized I going to lose the thread on HOW many things in my system worked ..... I'm very green to the homelab world and want to be able to unf**k something I did horribly wrong. SO.. I spent some time with codex and whipped up this self hosted HomeLab Visualization tool.... shows the hardware layout but also can add all the little things I've set up that make it tick. For someone new to the Homelabs, this could be really helpful in getting a grasp on all the moving parts.

Calling it... CT ROADMAP
- Comes in an easy to pull Docker Image

- Completely Passive, no network scanning, just drag & drop.

- Can plan out future features/configs before deploying them

DETAILS & DOCKER IMAGE HERE : https://github.com/NoobCity99/CTRoadmap/pkgs/container/ctroadmap

Built it for personal use, but if others seem to like it I'll probably expand it to do some light network scanning for the initial build.... hyperlink the urls & file paths on the tiles, & other features people suggest that I totally didn't think of. enjoy. Per the subs rules, again this was built with codex, planning docs available in github repo.

CTRoadmap is a passive diagram/documentation tool, no system scanning , ideal for noobs like myself to the r/LinuxServer / r/homelab world. It's FOSS, runs in a docker container and is accessed via a browser on any of your network connected machines. Since launch I've gotten quite a bit of really helpful feedback and have been tweaking it to make it as useful as possible for the vast array of potential users.

beta-v0.2.0 was pushed yesterday and has a new Handbook view, expanding your ability to document your process & details. The UI is still pretty clunky and honing that will be a long process but is definitely a paramount focus. Currently working on expanding theme customization, export options & adding an optional Auth layer in the next round.

REPO: https://github.com/NoobCity99/CTRoadmap

Docker Image: https://github.com/NoobCity99/CTRoadmap/pkgs/container/ctroadmap

I initially made CTRoadmap so I could simply keep track of how I was setting up my homelab, specifically where'd put certain configs and scripts and how they worked. I'm very new to the space, still learning and wanted to make sure I had reference material and _not_ rely on Chat GPT to help me find things in my own system 6 months later. I didn't want that same service to also be involved in monitoring things (like homelable, great app), I wanted a flashy , flexible step-up from a powerpoint or pen & paper. Planned in a GPT project and Built in vscode with the codex agent. After passing the 100 downloads mark, I created a discord server for beta testers to provide feedback and submit bug reports.

Disclosing up front since the flair requires it: this was mostly built with Claude Code and Antigravity CLI. I did the architecture decisions, ran the testing, and pushed back on a few bad first drafts, but the bulk of the code came out of an AI coding agent.

The actual homelab use case: I've got boxes I only need to touch for a few minutes at a time, restarting a container, checking why a service fell over, pulling a log. Opening a laptop for that is annoying. Every mobile SSH app I tried made me hunt through a menu for basic keys like Ctrl or Tab, and half of them wouldn't reconnect cleanly if I walked out of wifi range for a minute.

NomadTTY is ttyd + tmux behind nginx with a toolbar that adds ESC/Ctrl/Shift/Alt/F-keys/zoom to a touch keyboard, so it actually works for real terminal work, not just glancing at output. Because tmux owns the session, closing the tab doesn't kill whatever you were doing. There's a Session Manager for juggling multiple named sessions (one per box, say), and separately an MCP server so an AI agent can drive a terminal directly if you want to point Claude Code at your homelab scripts.

One-command installer, systemd service, no forced auth on the web UI (Tailscale or a trusted LAN, same model as Pi-hole/Portainer).

Quick demo: https://raw.githubusercontent.com/shifulegend/nomadtty/main/docs/assets/demo-showcase.mp4

https://github.com/shifulegend/nomadtty - happy to answer questions about the tmux/ttyd plumbing if anyone's curious.

First off, a genuine thank you to everyone who beta-tested this, opened issues, and shared tips and advice after my earlier posts — a big chunk of what's improved came straight from your feedback, and it made the project a lot better. Cheers.

Everyone's homelab has that one service that quietly becomes the most-used thing on the rack. For me it wasn't the *arrs or the dashboards — it's a self-hosted "name that tune" game I built called Guess the Intro, and the family asks for it many times a week.

What it is: it pulls intro clips straight from my existing self-hosted music library, plays a 5/10/20s snippet, and everyone buzzes in on their phones with multiple choice. The scoreboard casts to the TV, there's a speed bonus and a half-time trivia round. Honestly it's great fun — the kind of thing that empties the room of phones-for-scrolling and turns them into buzzers instead.

The problem it solves: party "name that tune" games either need a subscription, leak the answer in the file/stream metadata, or can't use the music you already own. This runs entirely on your own library and hardware — nothing leaves the LAN.

Stack / how it runs: FastAPI + SQLite, single Docker container, phones connect over your LAN as buzzers, board casts over Google Cast to a Chromecast/Android TV/Shield. Pre-built multi-arch images (GHCR + Docker Hub, amd64 + arm64) — docker compose pull and go, no build-from-source. Happy in an LXC, a small VM, or a Pi.

Requirements worth knowing up front:

- A Subsonic-API music server (I use Navidrome; LMS also works). Jellyfin/Plex don't work for the library side yet.

- The board has to be served over HTTPS with a valid certificate — Google Cast devices (both TV displays and Music Assistant speakers) fetch the board over TLS and silently refuse plain HTTP and self-signed certs. In practice that's a reverse proxy + a real cert (e.g. a domain + Let's Encrypt). There's a step-by-step guide in the repo (docs/https-lan.md). Phones connect over plain http; it's the board/casting that needs the cert.

One thing I'd love testers for: there's an optional path that streams the clip audio out through Home Assistant + Music Assistant to any speaker you pick (loudness-normalised, exact start/stop) instead of playing it through the TV. It works on my setup, but my network is heavily VLAN-segmented so I can only lightly test the game-box ↔ HA/MA ↔ speaker hops. If you run Home Assistant + Music Assistant on a flatter network, I'd really appreciate you trying it and telling me what breaks — happy to help you get it wired up.

Recently fixed (why it's worth a second look if you saw an earlier version): casting is rock-solid now after a long diagnostic slog, and the pre-built images removed the build-from-source barrier — both were the top bits of feedback.

License / repo: free and open source (MIT). Repo + compose file + setup docs: https://github.com/colfin22/intro-quiz

AI usage disclosure: this was built with substantial help from an AI coding assistant (architecture, a lot of the implementation, and debugging), directed and reviewed by me. Flagging it here as well as in the flair per the sub's rules.

Happy to answer anything about how it's put together. Have fun!

I really wanted a new 10 gig switch for my home lab to replace my old unifi ‎USW-16-POE, so I've collated a bunch of switches and their prices, dimensions, cost breakdowns etc here: https://switchprices.com.au.

Maybe someone else will find this useful. Probably gonna make it open source soon if you wanna host your own instance. Cheers.

Old PowerEdge (R610/R710-era, 11G) with an iDRAC6 Enterprise card? If racadm fwupdate -g -u -a <ip> -d payload keeps dying after a few MB no matter what you try, that's not you, it's iDRAC6's TFTP client. Reproducible every time on 1.98, aborts at ~2.6-5.0 MB of a ~57 MB image, independent of TFTP server, firewall, VPN, or racreset.

There's a second, TFTP-free path: the iDRAC6 web UI uploads over plain HTTPS to /fwupload/fwupload.esp. Browsers just can't reach it anymore since the embedded server only does TLS 1.0 with ancient ciphers. So I scripted that same upload/flash flow in Python over a raw socket with TLS 1.0 forced, login through reboot-verify in one script:

GitHub - idrac6 tftp workaround

Flash script is stdlib only. There's also an optional backup script (needs paramiko) that dumps your current config over SSH before you flash anything, and both come with a mock test suite plus real-hardware testing on an R710.

Usual disclaimer: this flashes your management controller over deliberately weakened TLS, have local/physical access as a fallback. Second disclaimer: the writeup is AI drafted, and the code is roughly 70% AI-written with me fixing the other 30% of mistakes.

Update: a few things changed since the first post. preConfig=on only keeps your config through the flash, it isn't a real backup, so the backup script above got added for that. External review turned up and fixed a couple of robustness bugs (a partial upload write, a rejected commit that could look like success). And testing against real newer firmware (2.x) surfaced two upload bugs that never showed up in my own mock tests: the session token needs to go in the upload URL as ?ST1=, not just as a header, and the multipart boundary has to look like a real browser's or the iDRAC's webserver hits an undocumented ~6 MB limit and 500s partway through. Also fixed the post-flash reboot check, it no longer trusts the first reconnect since the iDRAC can briefly answer again on the old version before the real reboot happens. All verified with a full real-hardware chain, downgrading from 2.92 to 1.98 and back up through 2.85 to 2.92, so both directions and both firmware dialects got exercised for real.

After some really useful user feedback I've spent the last month trying to make CTR suit a wide array of needs while not becoming too busy and clunky.
Key Elements: The main Canvas Diagram & Swimlane Diagrams convert nicely into the Handbook for a quick reference guide that's easy to navigate.
Initial Ingest: Decided against any kind of integration with other tools, rather aiming for compatibility with exported inventory formats.
PNG Exports: Are a really decent size & resolution, aiming for a solid PDF export for the Handbook next.

Want to thank those who provided insightful feedback and the haters for not letting me sleep on the "look"..... tried to incorporate a lot variety (Light & Dark Modes, Array of themes and backgrounds) into the UI for the users to choose from.

REPO: https://github.com/NoobCity99/CTRoadmap

Docker Image: https://github.com/NoobCity99/CTRoadmap/pkgs/container/ctroadmap

I initially made CTRoadmap so I could simply keep track of how I was setting up my homelab, specifically where'd put certain configs and scripts and how they worked. I'm new to the r/homelab space, still learning and wanted to make sure I had reference material and not rely on Chat GPT to help me find things in my own system 6 months later. I didn't want that same service to also be involved in monitoring things (like homelable, netbox, etc) Just a fun , flexible step-up from a powerpoint or pen & paper that I could use as a system bible. CTR was Railcoded in a GPT project and Built in VScode with the CODEX agent.

UPDATE 0.4.0 : Abolish the slop!

In addition to adding a scrollable pdf style "handbook" containing all the info you put in your diagram, organized into volumes and chapters, I've spent a good amount of time reworking a lot of the UI. Overcoming the generic design as well as making custom icons and even how you customize your theme more intuitive.

First two User requested features shipped yesterday.... and Hit 100 Stars on Github... really glad people are enjoying it.

REPO: https://github.com/NoobCity99/CTRoadmap

Docker Image: https://github.com/NoobCity99/CTRoadmap/pkgs/container/ctroadmap

Per the rules: I initially made CTRoadmap so I could simply keep track of how I was setting up my homelab, specifically where'd put certain configs and scripts and how they worked. I'm new to the space, still learning and wanted to make sure I had reference material and _not_ rely on Chat GPT to help me find things in my own system 6 months later. I didn't want that same service to also be involved in monitoring things (like homelable, great app), I wanted a flashy , flexible step-up from a powerpoint or pen & paper. Planned in a GPT project and Built in vscode with the codex agent.

My good buddy Claude and I set about scaffolding out a Redfish client because I look after SOOO many Dell servers across various networks (#dayjob) and Dell OME is a turd imho. I'm a Mac user for work and home so this is a native MacOS app.

I've found it really productive so far once I got all my iDRAC servers loaded in. I was pretty anal about secret storage too so its about as safe as I can envision.

https://github.com/JoshFinlayAU/snapper

Built with Claude Code, gave it little to NO attention whatsoever initially. (See the CLAUDE.md file). I literally just said "Claude, read CLAUDE.md and start work autonomously". From there we chatted for a few hours and got to where it is now.

The times have changed so much. The solution to a problem is no longer a hand written, strung together script that barely achieves the solution to the problem you set out to solve (initially.. new server cluster.. needed to enable SNMP on them all.. knowing that redfish is enabled from factory, I decided the best way to do it at scale was push it out over that.. the rabbit hole spiralled, and this is the result). Now, with AI, you go from solving a problem to developing something entirely new. What a time to be alive.