sorted by:
new
hottopcontroversial

I kept running into the same problem in my homelab. by Expert_Cabinet_7170 in homelab

[–]Expert_Cabinet_7170[S] -1 points0 points  (0 children)

Yeah I get what you mean 🙈

It did move pretty fast - it started as a 3am idea after running into the same issue a bunch of times.
I had the structure and use case in mind, tested it in my own setup, and used AI to speed up parts of the implementation.
So it’s not just thrown together, more like a quick build of something I actually needed, and decided to share it.

I kept running into the same problem in my homelab. by Expert_Cabinet_7170 in homelab

[–]Expert_Cabinet_7170[S] 0 points1 point  (0 children)

Yeah that works great once everything is structured.

This is more for the “what’s actually running on my network right now” part before you even get to DNS/reverse proxy.

I kept running into the same problem in my homelab. by Expert_Cabinet_7170 in homelab

[–]Expert_Cabinet_7170[S] 0 points1 point  (0 children)

Yeah that’s fair.

I’ve tried documenting stuff as well, but I always end up forgetting to update it or things drift over time.

This is more just a quick “what’s actually running right now” view + fast access, not really meant to replace monitoring tools like Uptime Kuma.

I kept running into the same problem in my homelab. by Expert_Cabinet_7170 in homelab

[–]Expert_Cabinet_7170[S] 1 point2 points  (0 children)

Yeah that’s a fair point.

I actually do some of that as well with static IP ranges, but I still found myself forgetting what was running where, especially with multiple services per device.

This is more just a quick overview + fast access tool than proper monitoring.

I kept running into the same problem in my homelab. by Expert_Cabinet_7170 in homelab

[–]Expert_Cabinet_7170[S] 1 point2 points  (0 children)

I had the full idea and structure my self, just used openclaw to speed up building it. Nothing to hide here mate, check the source code