-
-
-2. Install Nextflow if necessary
-
-```
-curl -s https://get.nextflow.io | bash
-```
-
-3. Create a Kubernetes persistent volume
-
-```
-kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/task-pv-volume.yaml
-```
-
-4. Create a Kubernetes persistent volume claim
-
-```
-kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/task-pv-claim.yaml
-```
-
-5. Run any Nextflow pipeline on your new kubernetes clusters
-
-```
-nextflow kuberun nextflow-io/rnatoy -v task-pv-claim:/mnt/
-```
-
-```
-
-```
diff --git a/public/css/custom.css b/public/css/custom.css
index 5af10128..07187a26 100644
--- a/public/css/custom.css
+++ b/public/css/custom.css
@@ -1003,6 +1003,9 @@ a.carousel-arrow-next {
width: 100%;
}
}
+.blg-text > p > img {
+ margin: 1em 0;
+}
.blg-social {
list-style-type: none;
margin: 0;
diff --git a/src/content/blog/2016/enabling-elastic-computing-nextflow.md b/src/content/blog/2016/enabling-elastic-computing-nextflow.md
index 20a4bec8..e3d95a43 100644
--- a/src/content/blog/2016/enabling-elastic-computing-nextflow.md
+++ b/src/content/blog/2016/enabling-elastic-computing-nextflow.md
@@ -21,7 +21,7 @@ This solution is characterised by using a lean application stack which does not
require any third party component installed in the EC2 instances other than a Java VM and the
Docker engine (the latter it's only required in order to deploy pipeline binary dependencies).
-
+
Each EC2 instance runs a script, at bootstrap time, that mounts the [EFS](https://aws.amazon.com/efs/)
storage and downloads and launches the Nextflow cluster daemon. This daemon is self-configuring,
diff --git a/src/content/blog/2017/nextflow-and-cwl.md b/src/content/blog/2017/nextflow-and-cwl.md
index f94f041b..ae0a8e27 100644
--- a/src/content/blog/2017/nextflow-and-cwl.md
+++ b/src/content/blog/2017/nextflow-and-cwl.md
@@ -28,9 +28,7 @@ subworkflows are not supported, each step must be a CWL `CommandLineTool` file.
The image below shows an example of the major components in the CWL files and then post-conversion (click to zoom).
-
-
-
+[](/img/cwl2nxf-min.png)
CWL and Nextflow share a similar structure of defining inputs and outputs as shown above.
diff --git a/src/content/blog/2017/nextflow-hack17.md b/src/content/blog/2017/nextflow-hack17.md
index 8cbfcfc9..49fd2b26 100644
--- a/src/content/blog/2017/nextflow-hack17.md
+++ b/src/content/blog/2017/nextflow-hack17.md
@@ -39,7 +39,7 @@ An image of the example report is shown below with the interactive HTML availabl
[here](/misc/nf-trace-report.html). It is expected to be merged into the main branch of Nextflow
with documentation in a near-future release.
-
+
### Nextflow pipeline for 16S microbial data
diff --git a/src/content/blog/2017/nextflow-workshop.md b/src/content/blog/2017/nextflow-workshop.md
index 8775d58b..8a2ee7f7 100644
--- a/src/content/blog/2017/nextflow-workshop.md
+++ b/src/content/blog/2017/nextflow-workshop.md
@@ -177,4 +177,4 @@ The registration form is [available here](http://apps.crg.es/content/internet/ev
+
diff --git a/src/content/blog/2018/nextflow-turns-5.md b/src/content/blog/2018/nextflow-turns-5.md
index 99709370..0dc92b0e 100644
--- a/src/content/blog/2018/nextflow-turns-5.md
+++ b/src/content/blog/2018/nextflow-turns-5.md
@@ -31,7 +31,11 @@ There is also a Python package with helper tools for Nextflow.
You can find more information about the community via the project [website](https://nf-core.github.io), [GitHub repository](https://github.com/nf-core), [Twitter account](https://twitter.com/nf_core) or join the dedicated [Gitter](https://gitter.im/nf-core/Lobby) chat.
-
+
+
### Improved reporting and notifications
@@ -57,14 +61,21 @@ There has also been additions to workflow notifications. Currently these can be
Writing workflows no longer has to be done in monochrome. There is now syntax highlighting for Nextflow in the popular [Atom editor](https://atom.io) as well as in [Visual Studio Code](https://code.visualstudio.com).
-
-
+
+
### Conclusion
diff --git a/src/content/blog/2021/nextflow-developer-environment.md b/src/content/blog/2021/nextflow-developer-environment.md
index aab40d63..6be71a90 100644
--- a/src/content/blog/2021/nextflow-developer-environment.md
+++ b/src/content/blog/2021/nextflow-developer-environment.md
@@ -28,7 +28,7 @@ Nextflow pipelines can be written in any plain text editor. I'm personally a bit
My current choice is Visual Studio Code which provides a wealth of add-ons, the most obvious of these being syntax highlighting. With [VSCode installed](https://code.visualstudio.com/download), you can search for the Nextflow extension in the marketplace.
-
+
Other syntax highlighting has been made available by the community including:
@@ -46,7 +46,7 @@ Start the Nextflow console with the following command:
$ nextflow console
```
-
+
Use the `CTRL+R` keyboard shortcut to run (`⌘+R`on the Mac) and to evaluate your code. You can also evaluate by selecting code and use the **Run selection**.
@@ -70,7 +70,7 @@ To learn more about building Docker containers, see the [Seqera Labs tutorial](h
Additionally, you can install the VSCode marketplace addon for Docker to manage and interactively run and test the containers and images on your machine. You can even connect to remote registries such as Dockerhub, Quay.io, AWS ECR, Google Cloud and Azure Container registries.
-
+
### 5. Use Tower to monitor your pipelines
@@ -106,7 +106,7 @@ or
$ pip install nf-core
```
-
+
### Conclusion