Closed bsweger closed 1 month ago
Curious to hear @elray1's feedback on this. This package isn't something we're actively collaborating on with people outside of our org, and we already have it Dockerized.
For those reasons, I wouldn't consider this one a high priority, but putting it out there to see what people think.
If we do end up using a script or makefile to do this, here's the incantation to install the nextclade CLI into the executable folder of the currently active Python venv:
curl -fsSL "https://github.com/nextstrain/nextclade/releases/latest/download/nextclade-x86_64-apple-darwin" -o "$VIRTUAL_ENV/bin/nextclade" && chmod +x $VIRTUAL_ENV/bin/nextclade
(a shortcut because the activated virtual env is already in the PATH)
Closing this one because we Dockerized the setup a few months ago.
Background
Due to the external tools used in this package, there are some moving parts that make it tedious to set up a development environment.
For example, neither of these non-Python dependencies can be installed via
pip
:Definition of done