Support use of Gource custom log output

[james-innes]

I have a large number of repos for which I can create a combined custom gource log however I am currently unable to pass this to the envisaged container.

We have the option to mount a local repository on container creation instead of providing a repo url so there could also be the option to mount a local file combo.log for processing instead.

Gource GitHub Wiki: Visualizing Multiple Repositories

[james-innes]

I was thinking something like this

[Cartoonman]

@asos-jamesinnes Might be worth taking a look at my fork: https://gitlab.com/Cartoonman/Envisaged-Redux (Github mirror: https://github.com/Cartoonman/Envisaged-Redux)

Currently the logic I use for multi-repo setup is that you can provide a directory that contains repositories, and it will add each one and do all of the work needed to merge them into one for Gource. It does not currently do recursive searches and will only search a depth of 1 for repos. It can however recurse through submodules if any repos have them if specified to.

A custom log input file is a good idea and is certainly worth adding later on.

[james-innes]

@Cartoonman Looks like you have some nice improvements over in your fork. Envisaged supports a mounted volume containing multiple repos. There will be cases in which people would like to create the commit log themselves. For example using authenticated Azure Repos: docker-gource-azure-repos In the mean time I am simply using docker-gource-mesa

[jamesbrink]

@Cartoonman I really like what you've done. I am always struggling to find time to work on this stuff, if you are interested here are some other things you might want to consider adding

https://gist.github.com/jamesbrink/6c07ca0f406387dd5dc05ef93fafe265

These were some quick nasty scripts to do things like quad view layouts.. i would use them as a reference nothing more as they don't support scaling resolutions.

I am going to try to find some time to dig into your fork but high level skim looks awesome!