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
Thanks for developing Nextflow and the complete universe of useful tools around it!
Recently, we got aware that Anaconda Inc. changed its Terms and Conditions for the usage of their "defaults" channel. Institutions larger than 200 employees may get charged quite considerable sums.
The documentation in https://github.com/nextflow-io/nextflow/blob/master/docs/conda.md lists "defaults" channel.
Could it be useful to highlight the potential issues in a disclaimer there, make the use of the "defaults" channel optional or remove the "defaults" channel from the examples?
cheers
The text was updated successfully, but these errors were encountered:
@ewels how do you think we should update the conda yaml examples on the conda docs page? is it safe to just remove defaults in both cases? I can't remember how it works without the defaults channel
Yes it's fine to remove defaults. We've already done this everywhere in the code a while back, I didn't realise that any were left in the docs. We should just remove those lines.
Hi!
Thanks for developing Nextflow and the complete universe of useful tools around it!
Recently, we got aware that Anaconda Inc. changed its Terms and Conditions for the usage of their "defaults" channel. Institutions larger than 200 employees may get charged quite considerable sums.
The documentation in https://github.com/nextflow-io/nextflow/blob/master/docs/conda.md lists "defaults" channel.
Could it be useful to highlight the potential issues in a disclaimer there, make the use of the "defaults" channel optional or remove the "defaults" channel from the examples?
cheers
The text was updated successfully, but these errors were encountered: