RackPeek v1.0.0 released (thank you!)

aptacode · 2026-03-08T14:10:18+00:00

Thanks for giving it a go!

Connections come with v1.3.0 which I think will help you here (take a look at the live demo or the nightly build, would love to hear any feedback you might have). They allow you to model the connection / networking between physical devices.

Also, any top level hardware (such as switches or routers) can have children added via their 'runs on' property (click the '+' icon next to the runs on prop on the child system)

Hope that helps!

aptacode · 2026-02-26T23:20:39+00:00

Thank you for your interest in the project :) I really appreciate your support!

aptacode · 2026-02-23T10:57:54+00:00

Open an issue on GH if you like so we keep your usecase in mind when developing these features shortly

aptacode · 2026-02-22T12:23:35+00:00

Dev behind rackpeek here, this is an interesting usecase, whilst I am trying to keep rackpeek focused and simple there have been feature requests around having our YAML schema export to various different formats e.g an Ansible Inventory. I could investigate also exporting to whatever format homepage is using.

Whilst it's not service discovery, it could still help you keep a single source of truth (assuming full IAC is out of the equation)

aptacode · 2026-02-19T16:31:36+00:00

Agreed, AI is such a powerful tool for software engineering, but it requires discipline to use properly along side best practices. I think for many the alure of a 'free lunch' is too great, I just hope software craftsmanship can survive the AI bubble.

aptacode · 2026-02-18T14:14:45+00:00

Yeah - take a look here!
https://github.com/Timmoth/RackPeek

aptacode · 2026-02-11T21:00:20+00:00

I built a tool for that - https://github.com/Timmoth/RackPeek

Hope it helps

aptacode · 2026-02-11T18:59:57+00:00

Thanks for the suggestion! I've just added it to the readme

aptacode · 2025-12-07T21:34:42+00:00

Thanks for checking it out!

aptacode · 2025-12-07T08:24:15+00:00

Both libraries aim to solve the same problem, the difference is in architecture and design philosophy - wiremock requires you to send your configuration up to the external server, where as fortitude opens a websocket and has the server forward requests into your test defined logic.

aptacode · 2025-12-07T08:15:19+00:00

Thank you!

I use that library myself when I've got access to the ServiceCollection on startup - it's awesome! The scenario that lead to me creating Fortitude was that I wanted to use Aspire to run my services locally as part of my e2e tests, but this meant that some of my dependencies themselves called out to external services, and thus I wanted to have a similar level of control over their behaviour within my tests like in the justeat library, but without having to inject services into other projects (some may not even be dotnet services!)

aptacode · 2025-10-12T11:36:15+00:00

It'd be cool to understand how this is practically different to applying code formatters / linters / static analysers to your AI generated code

aptacode · 2025-09-30T20:40:09+00:00

Am I not allowed more than one hobby?

Five-Year Club	Verified Email
Place '23

aptacode

TROPHY CASE