Download bridgedb upon first run of docker

[nunogit]

Advantages:

• smaller initial footprint on images
• we can allow specie selection for db (upon first run)

Disadvantes:

• we should check if this is according to Docker philosophy
• how to manage versions of BDB inside the containers, namely for reproducibility?
• we can't tie bdb versions to tag distributions

[egonw]

Sounds reasonable to me. Alternatively, the Docker image would distribute the archived version and decompress upon first run. But whatever you think is best, works for me

[egonw]

BridgeDb 2.3.0 is released.

[egonw]

Ping, what is the status of this?

[marvinm2]

It is now included in the image with pre-set mapping files. Not a selection on first run, as described by Nuno. Could push various versions with different mapping possibilities (selections, only human, or all).

By the way, why is it not possible to tie bridgedb versions to tags? We can make custom singular tags that contain various types of info like bdb version + mappings included. If we would then describe what these tag structures mean, it would solve that right? Or am I missing the point here?