<@UE4L64T4G> is this still true? <https://github.c...
# wg-container-conversion-task-force
m
@Phil Ewels is this still true? https://github.com/nextflow-io/nextflow/issues/5583#issuecomment-2875484270 If so, that's a blocker for the container configs
p
I'm not sure, but why would it be a blocker?
We're going to download these files and save them to the modules repo, so presumably we can rename these to whatever we want?
m
Ah, so we should write these local file paths in the config files then?
Because in the blog post we wrote the wave url
p
ah yeah, no I was thinking that we should save them in the modules repo
Mind you, we might have to also save in the pipeline if this is true:
and can't be remote files.
I've just kicked off Claude, can see if we can fix Nextflow to make this easier
But yeah, even if so it'll take a while to make it through. So maybe best to copy in - safest and probably not a terrible idea anyway