Automatically generate requirements.txt for each dockerfile creation / generation run

[DanNBullock]

I know that the structuring of this repo is directory based, such that each directory corresponds to a different dockerfile being produced, however it would be extremely useful for folks like myself looking for documentation of which modules (and which versions thereof) are included in these docker images. Unfortunately the brainlife dockerhub, and dockerhub in general, doesn't include information about the contents of dockers, so docker-theives like myself often have to search for dockerfile generation scripts (as stored here) or just guess and check.

Definitely not something that needs to be retroactively implemented, but would be nice to have in the future.

[DanNBullock]

Relatedly (and also possibly as a crazy idea), it seems that it may also be possible to design a bit of code to automatically pick viable containers for a given app repository (assuming there's a machine readable requirements.txt file).

If each of these directories had their own requirement.txt files, then the solution seems pretty straightforward. Even in the case that such requirement.txt files weren't available, it would still be not that difficult to iteratively check the dockerfile for each of these directories for the right string match.

Pseudo-code wise, I think it's as simple as iterating across each line of the query repository's requirement.txt file (i.e. the repository we're automatically trying to find a workable docker container for) and checking for a match in each of the dockerfiles in the directories of this repository. In this way you'd generate a boolean N x M matrix, where N = the number of directories (i.e. docker builds) in this repository, and M = the number of required modules in the query repository.

Perhaps this would be a bad / lazy practice, but it would make my life easier as I develop apps and try and find an existing docker image that meets my needs.