Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define path_to_fauna in config #86

Merged
merged 3 commits into from
Aug 22, 2024
Merged

Define path_to_fauna in config #86

merged 3 commits into from
Aug 22, 2024

Conversation

jameshadfield
Copy link
Member

The current value expects fauna to be a sister directory to 'ingest'. This is valid when we are using the docker runtime¹ as it mounts the 'ingest' folder to '/nextstrain/build' and fauna is 'nextstrain/fauna', but it almost never true when running outside of docker as that would require fauna to be within the 'avian-flu' repo. The docs do state that we must run in docker, but that's an overly strict requirement.

Addition context on slack https://bedfordlab.slack.com/archives/CD84ELG0N/p1723666776588239?thread_ts=1720569955.202459&cid=CD84ELG0N

¹ until we add a nextstrain-pathogen.yaml file

  • Checks pass

The current value expects fauna to be a sister directory to 'ingest'.
This is valid when we are using the docker runtime¹ as it mounts the
'ingest' folder to '/nextstrain/build' and fauna is 'nextstrain/fauna',
but it almost never true when running outside of docker as that would
require fauna to be within the 'avian-flu' repo. The docs do state that
we must run in docker, but that's an overly strict requirement.

Addition context on slack <https://bedfordlab.slack.com/archives/CD84ELG0N/p1723666776588239?thread_ts=1720569955.202459&cid=CD84ELG0N>

¹ until we add a nextstrain-pathogen.yaml file
This results in a different mount point for the 'ingest' directory in
docker runtimes which more closely matches a typical setup using other
runtimes. This allows the relative location of fauna ('path_to_fauna')
to be the same for a typical ambient setup as for docker.

See <nextstrain/cli#371 (comment)>
for more detail on mount points for the docker runtime.
@tsibley
Copy link
Member

tsibley commented Aug 20, 2024

Alternatively, why not add a nextstrain-pathogen.yaml file (it's probably gonna happen anyway at some point) and adjust the hardcoded value to ../../fauna? Extra config seems unnecessary at that point given conventions around fauna.

@jameshadfield
Copy link
Member Author

why not add a nextstrain-pathogen.yaml file

That was done via #87 which sits on top of this PR

@jameshadfield jameshadfield merged commit 0984ad8 into master Aug 22, 2024
2 checks passed
@jameshadfield jameshadfield deleted the james/fauna-path branch August 22, 2024 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants