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!
As the title said, I've created this tool so I can better visualize the infra of services that I work with, since, sometimes, it's quite hard to figure it out when I'm joining a new project.
Overall it should be quite simple to use, and to extend as well, since it's all based in a config.yaml file that will list the services and infra deps.
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!