Blog: Tweak config examples

[ewels]

I personally found the mix of configuration within script process blocks and config process scopes confusing. We always say that it's best practice to never specify this stuff within a script, but always do it in a config file - that way it's easier to overwrite and make the pipeline portable. As such, I updated the examples to all use only configs and not script syntax.

One or two other minor tweaks.

[netlify]

✅ Deploy Preview for nextflow-staging ready!

Name	Link
🔨 Latest commit	3b14a36
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-staging/deploys/646f563b6e8cdc0008040cb3
😎 Deploy Preview	https://deploy-preview-115--nextflow-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[GJSissons]

Thanks for these corrections, @ewels. The changes look good to me. I can see where it makes more sense to specify the settings in the config file. I notice in the documentation settings often appear in the process block in the workflow itself, but maybe this is just for ease of explanation, or these haven't been updated yet. https://nextflow.io/docs/latest/process.html#process-cpus

[ewels]

Yeah, that's because they are process directives - so they sit in the documentation for processes. The config docs just says "you can do all the process directives". It's not wrong to do it in the process, just that we typically don't consider it best practice.

[ewels]

@GJSissons NB couple of other more subtle changes highlighted 👇🏻

[ewels]

Removed as this isn't explained until the following section. Alternatively could reorder the sections, or just leave it here without explanation is probably fine too.