Update links to point to new Nextflow docs

Author: christopher-hakkaart

changelog/seqera-enterprise/v22.3.md

@@ -47,7 +47,7 @@ This feature is currently only available on Tower Cloud (tower.nf). For more inf
 
 ### Wave containers (technology preview)
 
-Tower now supports the Nextflow [Wave](https://www.nextflow.io/docs/latest/wave.html) container provisioning and augmentation service. When a pipeline is run in Nextflow using Wave, the Wave service uses a Dockerfile stored in the process directory to build a container in the target registry. When the container to be used for process execution is returned, the Wave service can add functional layers and data on-the-fly before it is returned to Nextflow for actual process execution.
+Tower now supports the Nextflow [Wave](https://docs.seqera.io/nextflow/wave) container provisioning and augmentation service. When a pipeline is run in Nextflow using Wave, the Wave service uses a Dockerfile stored in the process directory to build a container in the target registry. When the container to be used for process execution is returned, the Wave service can add functional layers and data on-the-fly before it is returned to Nextflow for actual process execution.
 
 Wave also enables the use of private container registries in Nextflow — [registry credentials](https://docs.seqera.io/platform-cloud/credentials/overview) stored in Tower are used to authenticate to private container registries with the Wave service.
 

changelog/seqera-enterprise/v22.4.md

@@ -33,7 +33,7 @@ The **All runs** view is accessible via the user menu.
 
 ### Wave support for Tower Enterprise
 
-All Tower instances with internet access can now connect to the Seqera Labs Wave container service to leverage its container augmentation and Fusion v2 file system capabilities. See the [Wave containers documentation](https://www.nextflow.io/docs/latest/wave.html) for more information about Wave containers.
+All Tower instances with internet access can now connect to the Seqera Labs Wave container service to leverage its container augmentation and Fusion v2 file system capabilities. See the [Wave containers documentation](https://docs.seqera.io/nextflow/wave) for more information about Wave containers.
 
 The Wave integration also allows for the secure transfer of credentials required to access private registries between services. See the [Tower documentation](https://docs.seqera.io/platform-enterprise/23.3) to learn how to use the feature in your enterprise installation.
 

changelog/seqera-enterprise/v23.4.md

@@ -62,7 +62,7 @@ The Docker Compose CLI plugin replaces the standalone `docker-compose` binary, w
 
 **Cloud compute environments use cloud cache by default**
 
-When a cloud storage location is provided as the pipeline work directory in a cloud compute environment, a scratch folder is created in that location to be used for the Nextflow process cache by default. This can be overridden with an alternate cache entry in your [Nextflow configuration](https://www.nextflow.io/docs/latest/process.html#process-cache).
+When a cloud storage location is provided as the pipeline work directory in a cloud compute environment, a scratch folder is created in that location to be used for the Nextflow process cache by default. This can be overridden with an alternate cache entry in your [Nextflow configuration](https://docs.seqera.io/nextflow/process).
 
 **Login redirection logic update**
 

changelog/seqera-enterprise/v25.1.md

@@ -105,7 +105,7 @@ Seqera Platform 25.1 includes Nextflow 24.10.5 (previously 24.10.4 from v24.2).
 
 According to the [24.10.0](https://github.com/nextflow-io/nextflow/releases/tag/v24.10.0) through [24.10.5](https://github.com/nextflow-io/nextflow/releases/tag/v24.10.5) release notes, this update includes improvements and bug fixes. Existing pipelines will continue to work.
 
-See the [Nextflow 24.10 migration guide](https://www.nextflow.io/docs/latest/migrations/24-10.html) for full details.
+See the [Nextflow 24.10 migration guide](https://docs.seqera.io/nextflow/migrations/24-10) for full details.
 
 :::note
 The default Nextflow version can be overridden by setting `NXF_VER` in a [pre-run script](https://docs.seqera.io/platform-enterprise/25.1/launch/advanced#pre-and-post-run-scripts):

changelog/seqera-enterprise/v25.2.md

@@ -41,7 +41,7 @@ Single instance compute environments create a single compute instance to execute
 ### Fusion
 
 - Added Fusion Snapshots (beta) support in AWS Batch compute environments, enabling Fusion to automatically restore jobs interrupted by AWS Spot instance reclamation. See [Fusion Snapshots](https://docs.seqera.io/fusion/guide/snapshots) for more information.
-- Fusion licensing enabled. A Fusion license sets a specific quota for Fusion use, measured by total pipeline throughput per month (defined by [Nextflow's I/O metrics](https://www.nextflow.io/docs/latest/tutorials/metrics.html#i-o-usage)). See [Fusion licensing](https://docs.seqera.io/fusion/licensing) for more information.
+- Fusion licensing enabled. A Fusion license sets a specific quota for Fusion use, measured by total pipeline throughput per month (defined by [Nextflow's I/O metrics](https://docs.seqera.io/nextflow/tutorials/metrics#i-o-usage)). See [Fusion licensing](https://docs.seqera.io/fusion/licensing) for more information.
 - Added a Platform Fusion usage dashboard.
 
 ### Audit logs
@@ -153,7 +153,7 @@ According to the [25.04.0](https://github.com/nextflow-io/nextflow/releases/tag/
 - AWS Java SDK upgraded from v1 to v2 (affects `aws.client` config options)
 - Package `nextflow.config.schema` renamed to `nextflow.config.spec`
 
-See the [Nextflow 25.04 migration guide](https://www.nextflow.io/docs/latest/migrations/25-04.html) for full details.
+See the [Nextflow 25.04 migration guide](https://docs.seqera.io/nextflow/migrations/25-04) for full details.
 
 :::note
 The default Nextflow version can be overridden by setting `NXF_VER` in a [pre-run script](https://docs.seqera.io/platform-enterprise/25.2/launch/advanced#pre-and-post-run-scripts):
@@ -175,7 +175,7 @@ If you're using AWS Batch, you will need to configure a custom job-definition an
 
 ### Removed `maxSpotattempts` setting from Platform
 
-Nextflow now handles this setting. See the [Nextflow reference documentation](https://www.nextflow.io/docs/latest/reference/config.html) for more information.
+Nextflow now handles this setting. See the [Nextflow reference documentation](https://docs.seqera.io/nextflow/reference/config) for more information.
 
 ### Legacy Seqera container image registry access ended June 1, 2025
 

changelog/seqera-enterprise/v25.3.1.md

@@ -35,7 +35,7 @@ According to the [25.10.0](https://github.com/nextflow-io/nextflow/releases/tag/
 - AWS Java SDK upgraded from v1 to v2 (affects `aws.client` config options)
 - Package `nextflow.config.schema` renamed to `nextflow.config.spec`
 
-See the [Nextflow 25.10 migration guide](https://www.nextflow.io/docs/latest/migrations/25-10.html) for full details.
+See the [Nextflow 25.10 migration guide](https://docs.seqera.io/nextflow/migrations/25-10) for full details.
 
 **Note:** The default Nextflow version can be overridden by setting `NXF_VER` in a [pre-run script](https://docs.seqera.io/platform-enterprise/25.3/launch/advanced#pre-and-post-run-scripts):
 ```bash

changelog/seqera-enterprise/v25.3.md

@@ -119,7 +119,7 @@ Seqera Platform 25.3 includes Nextflow 25.04.8 (previously 25.04.3 from v25.2).
 
 According to the [25.04.0](https://github.com/nextflow-io/nextflow/releases/tag/v25.04.0) through [25.04.8](https://github.com/nextflow-io/nextflow/releases/tag/v25.04.8) release notes, this update includes bug fixes and stability improvements. Existing pipelines will continue to work.
 
-See the [Nextflow 25.04 migration guide](https://www.nextflow.io/docs/latest/migrations/25-04.html) for full details.
+See the [Nextflow 25.04 migration guide](https://docs.seqera.io/nextflow/migrations/25-04) for full details.
 
 **Note:** The default Nextflow version can be overridden by setting `NXF_VER` in a [pre-run script](https://docs.seqera.io/platform-enterprise/launch/advanced#pre-and-post-run-scripts):
 ```bash

docusaurus.config.js

@@ -294,7 +294,7 @@ export default async function createConfigAsync() {
               protocol: 'https',
             },
           ],
-          apiKey: process.env.TYPESENSE_SEARCH_API_KEY,
+          apiKey: 'UUIEzlGORRp9lV5GndPR1zYBVBCPIJOl',                                                  
           connectionTimeoutSeconds: 2,
         },
         typesenseSearchParameters: {

fusion_docs/guide/aws-eks.md

@@ -165,4 +165,4 @@ To use Fusion without the need for escalating privileges, install the Nextflow [
 fusion.privileged = false
 ```
 
-To use a custom FUSE device plugin, specify it via the `k8s.fuseDevicePlugin` configuration option. See [Kubernetes](https://www.nextflow.io/docs/latest/reference/config.html#k8s) configuration options for details.
+To use a custom FUSE device plugin, specify it via the `k8s.fuseDevicePlugin` configuration option. See [Kubernetes](https://docs.seqera.io/nextflow/reference/config#k8s) configuration options for details.

fusion_docs/guide/gcp-batch.md

@@ -31,7 +31,7 @@ When Fusion v2 is enabled, the following virtual machine settings are applied:
 :::
 
 1. Provide your Google credentials via the `GOOGLE_APPLICATION_CREDENTIALS` environment variable
-or with the `gcloud` auth application-default login command. See [Credentials](https://www.nextflow.io/docs/latest/google.html#credentials) for more information.
+or with the `gcloud` auth application-default login command. See [Credentials](https://docs.seqera.io/nextflow/google#credentials) for more information.
 
 1. Add the following to your `nextflow.config` file: