This project here is to solve a problem that I had, which is that I find hard to wrap my head around how a system bind to each other parts, and, well, that's how graph-go was born, so that I could see it.
So, that's the second post about this that I made, and it's a update! Now we got full blown auto-discovery, which makes the config file a fallback for advanced users and the ui is less janky. So now it's possible to properly see environment of your system (so far only via the docker networks) easily.
I plan to add the support for orchestrators, starting with K8s, soon, so it wouldn't be limited only to docker environments.
Anyway, hope this helps someone! Contributions are more than accepted!
Hey there!
This project here is to solve a problem that I had, which is that I find hard to wrap my head around how a system bind to each other parts, and, well, that's how graph-go was born, so that I could see it.
So, that's the second post about this that I made, and it's a update! Now we got full blown auto-discovery, which makes the config file a fallback for advanced users and the ui is less janky. So now it's possible to properly see environment of your system (so far only via the docker networks) easily.
I plan to add the support for orchestrators, starting with K8s, soon, so it wouldn't be limited only to docker environments.
Anyway, hope this helps someone! Contributions are more than accepted!
Perfect timing! I was just about to venture into the forrest called legacy-cluster. This looks great! Thanks for re-sharing, will give it a spin.
Happy to hear that, hope it helps
if any problem arises, lmk if there's something I can help with