This tool would provide the most value when integrated with other web frontends to git. Since the webserving section of the code is so lightweight, this should not be hard to do.
One route might be to keep the existing webserver running on a different port to the other frontend and then embed the graph visualization via <iframe>. However that probably wouldn't allow the tight integration which would deliver most value, e.g. being able to click on a commit in the graph to visit that commit in the frontend. It would also suffer from the restriction of one graph server (and hence TCP port) per repository.
I'd love to hear ideas from web frontend maintainers on this.
This tool would provide the most value when integrated with other web frontends to git. Since the webserving section of the code is so lightweight, this should not be hard to do.
One route might be to keep the existing webserver running on a different port to the other frontend and then embed the graph visualization via
<iframe>
. However that probably wouldn't allow the tight integration which would deliver most value, e.g. being able to click on a commit in the graph to visit that commit in the frontend. It would also suffer from the restriction of one graph server (and hence TCP port) per repository.I'd love to hear ideas from web frontend maintainers on this.