Investigate methods to declare expected augur/fauna/… versions #3
Comments
tsibley
added a commit
that referenced
this issue
Jul 2, 2018
This is more standard (e.g. follows the 12 factor app pattern) and, as Trevor noted¹, is encouraged by lots of services like Travis CI and Heroku and EC2. It also means credentials are not visible in the output of `ps`, which is important for running on shared hosts. Unresolved is how to programmatically describe the requirements on the "envdir" module. This is an unresolved question for build requirements in general.² It may be that we sidestep that by accessing envdir through a nextstrain.build module that's always required to be available, as described in a proposal for refactoring shared functions.³ ¹ #4 ² #3 ³ #2
|
Closing this out for reasons similar to #2 As with that issue, please re-open if there's disagreement about closing. |
+1! nextstrain/public#7 has some related discussion (6 years later). |
|
Just going to mention that zika pipeline no longer uses "fauna" since January 2024 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure what this should look like, but it might be a very useful thing to have. On the other hand, if we're good at preserving backwards compat once augur stabilizes a bit, this may be mostly a non-issue. A topic to think about and discuss.
The text was updated successfully, but these errors were encountered: