we just merged a new sub-command to dev:

nf-core modules container create

reads the environment.yml and build the docker, singularity containers on seqera containers via wave (and also adds a conda-lock file) for amd64 and arm64. This is all part of our big plan to make move module containers to seqera containers, including auto-updates etc: https://nf-co.re/blog/2024/seqera-containers-part-2 For now it just build the containers and writes them in the container directive and the meta.yml. we will add more functionality soon™ (completely getting rid of the ternary and handle most things with the different platform configs). I would be happy to get this tested thoroughly, before rolling it out wider (you can use it by running

pip install --upgrade --force-reinstall git+<https://github.com/nf-core/tools.git@dev>

).

What effect will this have on running modules standalone with the new

nextflow module run

command? Will the module be able to access these configs?

No because they're at pipeline level / meta.yml a

Is the wave CLI an actual dependency then ?

I think it uses the API directly, so no

Allright that's good! Thanks

nope, we use the wave cli...

I take it all back..

I haven’t tried the feature yet, I can’t tell. I was just thinking with my hat of maintaining an install for multiple users while keeping the IT team happy 🙂 I don’t want to be pessimistic

currently looking into what we loose without the CLI

I have the source code for Seqera Containers, which is Python (FastAPI) back end. That uses the Wave CLI directly and does similar stuff. Let me know if I can be of any help.

Nice!

I would already be happy if i could use the same API URL for all calls 😬 https://github.com/seqeralabs/wave/issues/1067

Does the alpha2 stub really not work for all endpoints? confused dog

nope