A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

I made my first Nextflow plugin (<https://github.com/fulcrumgenomics/nf-dotenv|nf-dotenv>)!

For complex projects where some configuration is stored in the environment or in a dotenv file (<https://hexdocs.pm/dotenvy/dotenv-file-format.html|spec>, <https://docs.docker.com/compose/environment-variables/set-environment-variables/|example>) it would be nice to pull that config into the Nextflow scope. This plugin achieves that with the import of a single function.

I have a <https://github.com/fulcrumgenomics/nf-dotenv#a-real-world-example|mini real-world example in the README> for projects where we use Docker Compose to build, tag, label, and push to registry many images and also want Nextflow processes to stay in sync with those container versions.

I'd be curious to know what you think and if it could be useful to any of your projects. I have a <https://github.com/nextflow-io/plugins/pull/55|PR> up to include the plugin in the Nextflow registry, so until then, it can really only be used by being built locally.

That's awesome! As someone who's laptop disk is 80% `.env` files this will be really useful. Does it work in the config scope?

<@U0381D3F03T> I don't think it works in the config scope unfortunately...

Only processes and workflows as far as I can tell.

<https://www.nextflow.io/docs/latest/plugins.html#functions>

I too, love the `.env` file :sweat_smile:

<https://direnv.net/> is always with me as well

The plugin will let you override the filename so you can do `.env` or `.envrc` for this reason.