You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for static installs, presumably we can rely on having them each in a specific location that we pass into the docker container with -v.
for dynamic installs (e.g. spinning up EC2 instances) we'll have to either have a snapshot or a copy in a fast-to-download locale, and then provide mechanisms to put the databases in place before running the container.
which leads to the question: how do we specify external dependencies for each container?
and what about people with private databases? how do we specify them?
presumably this is a job for either CWL or whatever dependency tracking system we use (e.g. pydoit).
The text was updated successfully, but these errors were encountered:
e.g. sourmash and kaiju need big databases.
for static installs, presumably we can rely on having them each in a specific location that we pass into the docker container with -v.
for dynamic installs (e.g. spinning up EC2 instances) we'll have to either have a snapshot or a copy in a fast-to-download locale, and then provide mechanisms to put the databases in place before running the container.
which leads to the question: how do we specify external dependencies for each container?
and what about people with private databases? how do we specify them?
presumably this is a job for either CWL or whatever dependency tracking system we use (e.g. pydoit).
The text was updated successfully, but these errors were encountered: