Skip to content

Commit 6018e3c

Browse files
authored
Merge pull request #381 from nextflow-io/remove-tower.nf
Update seqera_platform.md
2 parents 3b0f56b + f4bee2a commit 6018e3c

File tree

1 file changed

+25
-28
lines changed

1 file changed

+25
-28
lines changed

docs/basic_training/seqera_platform.md

Lines changed: 25 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Seqera core features include:
1616

1717
!!! tip
1818

19-
[Sign up](https://cloud.tower.nf/) to try Seqera for free or request a [demo](https://seqera.io/demo/) for deployments in your own on-premise or cloud environment.
19+
[Sign up](https://cloud.seqera.io/) to try Seqera for free or request a [demo](https://seqera.io/demo/) for deployments in your own on-premise or cloud environment.
2020

2121
You can use Seqera Platform via either the **CLI**, through the **online GUI** or through the **API**.
2222

@@ -56,7 +56,7 @@ Where `eyxxxxxxxxxxxxxxxQ1ZTE=` is the token you have just created.
5656

5757
Check your `nextflow -version`. Bearer tokens require Nextflow version 20.10.0 or later and can be set with the second command shown above. You can change the version if necessary.
5858

59-
To submit a pipeline to a [Workspace](https://help.tower.nf/getting-started/workspace/) using the Nextflow command-line tool, add the workspace ID to your environment. For example:
59+
To submit a pipeline to a [Workspace](https://docs.seqera.io/platform/24.1/getting-started/workspace-setup) using the Nextflow command-line tool, add the workspace ID to your environment. For example:
6060

6161
```bash
6262
export TOWER_WORKSPACE_ID=000000000000000
@@ -74,15 +74,15 @@ nextflow run hello.nf -with-tower
7474

7575
You will see and be able to monitor your **Nextflow jobs** in Seqera Platform.
7676

77-
To configure and execute Nextflow jobs in **Cloud environments**, visit the [Compute environments section](https://help.tower.nf/compute-envs/overview/).
77+
To configure and execute Nextflow jobs in **Cloud environments**, visit the [Compute environments section](https://docs.seqera.io/platform/24.1/compute-envs/overview).
7878

7979
!!! exercise
8080

8181
Run the RNA-Seq `script7.nf` using the `-with-tower` flag, after correctly completing the token settings outlined above.
8282

8383
??? tip
8484

85-
Go to <https://tower.nf/>, login, then click the run tab, and select the run that you just submitted. If you can’t find it, double check your token was entered correctly.
85+
Go to <https://cloud.seqera.io/>, login, then click the run tab, and select the run that you just submitted. If you can’t find it, double check your token was entered correctly.
8686

8787
!!! cboard-list-2 "Summary"
8888

@@ -95,9 +95,9 @@ To configure and execute Nextflow jobs in **Cloud environments**, visit the [Com
9595

9696
To run using the GUI, there are three main steps:
9797

98-
1. Create an account and login into Seqera Platform, available free of charge, at [tower.nf](https://tower.nf).
99-
2. Create and configure a new [compute environment](https://help.tower.nf/compute-envs/overview/).
100-
3. Start [launching pipelines](https://help.tower.nf/launch/launchpad/).
98+
1. Create an account and login into Seqera Platform, available free of charge, at [cloud.seqera.io](https://cloud.seqera.io).
99+
2. Create and configure a new [compute environment](https://docs.seqera.io/platform/24.1/compute-envs/overview).
100+
3. Start [launching pipelines](https://docs.seqera.io/platform/24.1/launch/launchpad#launchpad).
101101

102102
### Configuring your compute environment
103103

@@ -111,23 +111,20 @@ Each compute environment must be pre-configured to enable Seqera Platform to sub
111111

112112
!!! tip "The following guides describe how to configure each of these compute environments."
113113

114-
* [AWS Batch](https://help.tower.nf/compute-envs/aws-batch/)
115-
* [Azure Batch](https://help.tower.nf/compute-envs/azure-batch/)
116-
* [Google Batch](https://help.tower.nf/compute-envs/google-cloud-batch/)
117-
* [Google Life Sciences](https://help.tower.nf/compute-envs/google-cloud-lifesciences/)
118-
* [IBM LSF](https://help.tower.nf/compute-envs/lsf/)
119-
* [Slurm](https://help.tower.nf/compute-envs/slurm/)
120-
* [Grid Engine](https://help.tower.nf/compute-envs/altair-grid-engine/)
121-
* [Altair PBS Pro](https://help.tower.nf/compute-envs/altair-pbs-pro/)
122-
* [Amazon Kubernetes (EKS)](https://help.tower.nf/compute-envs/eks/)
123-
* [Google Kubernetes (GKE)](https://help.tower.nf/compute-envs/gke/)
124-
* [Hosted Kubernetes](https://help.tower.nf/compute-envs/k8s/)
114+
* [AWS Batch](https://docs.seqera.io/platform/24.1/compute-envs/aws-batch)
115+
* [Azure Batch](https://docs.seqera.io/platform/24.1/compute-envs/azure-batch)
116+
* [Google Batch](https://docs.seqera.io/platform/24.1/compute-envs/google-cloud-batch)
117+
* [Google Life Sciences](https://docs.seqera.io/platform/24.1/compute-envs/google-cloud-lifesciences)
118+
* [HPC (LSF, Slurm, Grid Engine, Altair PBS Pro)](https://docs.seqera.io/platform/24.1/compute-envs/hpc)
119+
* [Amazon Kubernetes (EKS)](https://docs.seqera.io/platform/24.1/compute-envs/eks)
120+
* [Google Kubernetes (GKE)](https://docs.seqera.io/platform/24.1/compute-envs/gke)
121+
* [Hosted Kubernetes](https://docs.seqera.io/platform/24.1/compute-envs/k8s)
125122

126123
### Selecting a default compute environment
127124

128125
If you have more than one **Compute Environment**, you can select which one will be used by default when launching a pipeline.
129126

130-
1. Navigate to your [compute environments](https://help.tower.nf/compute-envs/overview/).
127+
1. Navigate to your [compute environments](https://docs.seqera.io/platform/24.1/compute-envs/overview).
131128
2. Choose your default environment by selecting the **Make primary** button.
132129

133130
**Congratulations!**
@@ -148,20 +145,20 @@ Launchpad automatically detects the presence of a `nextflow_schema.json` in the
148145

149146
!!! info
150147

151-
The parameter forms view will appear if the pipeline has a Nextflow schema file for the parameters. Please refer to the [Nextflow Schema guide](https://help.tower.nf/workflow-schema/overview) to learn more about the schema file use-cases and how to create them.
148+
The parameter forms view will appear if the pipeline has a Nextflow schema file for the parameters. Please refer to the [Nextflow Schema guide](https://docs.seqera.io/platform/24.1/pipeline-schema/overview) to learn more about the schema file use-cases and how to create them.
152149

153150
This makes it trivial for users without any expertise in Nextflow to enter their workflow parameters and launch.
154151

155152
![Pipeline parameters](img/launch_rnaseq_nextflow_schema.png)
156153

157154
### Adding a new pipeline
158155

159-
Adding a pipeline to the pre-saved workspace launchpad is detailed in full on the [Seqera webpage docs](https://help.tower.nf/launch/launch/).
156+
Adding a pipeline to the pre-saved workspace launchpad is detailed in full on the [Seqera webpage docs](https://docs.seqera.io/platform/24.1/launch/launchpad#add-new-pipeline).
160157

161158
In brief, these are the steps you need to follow to set up a pipeline.
162159

163160
1. Select the Launchpad button in the navigation bar. This will open the **Launch Form**.
164-
2. Select a [compute environment](https://help.tower.nf/compute-envs/overview).
161+
2. Select a [compute environment](https://docs.seqera.io/platform/24.1/compute-envs/overview).
165162
3. Enter the repository of the workflow you want to launch. e.g. <https://github.com/nf-core/rnaseq.git>
166163
4. Select a workflow **Revision number**. The Git default branch (main/master) or `manifest.defaultBranch` in the Nextflow configuration will be used by default.
167164
5. Set the **Work directory** location of the Nextflow work directory. The location associated with the compute environment will be selected by default.
@@ -177,7 +174,7 @@ In brief, these are the steps you need to follow to set up a pipeline.
177174
178175
!!! info
179176
180-
Nextflow workflows are simply Git repositories and can be changed to any public or private Git-hosting platform. See [Git Integration](https://help.tower.nf/git/overview/) in the Seqera Platform docs and [Pipeline Sharing](https://www.nextflow.io/docs/latest/sharing.html) in the Nextflow docs for more details.
177+
Nextflow workflows are simply Git repositories and can be changed to any public or private Git-hosting platform. See [Git Integration](https://docs.seqera.io/platform/24.1/git/overview) in the Seqera Platform docs and [Pipeline Sharing](https://www.nextflow.io/docs/latest/sharing.html) in the Nextflow docs for more details.
181178
182179
!!! note
183180
@@ -191,7 +188,7 @@ In brief, these are the steps you need to follow to set up a pipeline.
191188
192189
To create your own customized Nextflow Schema for your workflow, see the examples from the `nf-core` workflows that have adopted this approach. For example, [eager](https://github.com/nf-core/eager/blob/2.3.3/nextflow_schema.json) and [rnaseq](https://github.com/nf-core/rnaseq/blob/3.0/nextflow_schema.json).
193190

194-
For advanced settings options check out this [page](https://help.tower.nf/launch/advanced/).
191+
For advanced settings options check out this [page](https://docs.seqera.io/platform/24.1/launch/launchpad#advanced-settings).
195192

196193
There is also community support available if you get into trouble, join the Nextflow Slack by following this [link](https://www.nextflow.io/slack-invite.html).
197194

@@ -205,19 +202,19 @@ There is also community support available if you get into trouble, join the Next
205202

206203
## API
207204

208-
To learn more about using the Seqera Platform API, visit the [API section](https://help.tower.nf/api/overview/) in this documentation.
205+
To learn more about using the Seqera Platform API, visit the [API section](https://docs.seqera.io/platform/24.1/api/overview) in the documentation.
209206

210207
## Workspaces and Organizations
211208

212209
Seqera Platform simplifies the development and execution of pipeline by providing a centralized interface for users and organizations.
213210

214-
Each user has a unique **workspace** where they can interact and manage all resources such as workflows, compute environments and credentials. Details of this can be found [here](https://help.tower.nf/getting-started/workspace/).
211+
Each user has a unique **workspace** where they can interact and manage all resources such as workflows, compute environments and credentials. Details of this can be found [here](https://docs.seqera.io/platform/24.1/getting-started/workspace-setup).
215212

216213
Organisations can have multiple workspaces with customized access for specific organisation **members** and **collaborators**.
217214

218215
### Organization resources
219216

220-
You can create your own organization and participant workspace by following the docs at [Seqera](https://help.tower.nf/orgs-and-teams/workspace-management/).
217+
You can create your own organization and participant workspace by following the docs at [Seqera](https://docs.seqera.io/platform/24.1/orgs-and-teams/workspace-management).
221218

222219
Seqera Platform allows the creation of multiple organizations, each of which can contain multiple workspaces with shared users and resources. This allows any organization to customize and organize the usage of resources while maintaining an access control layer for users associated with a workspace.
223220

@@ -227,7 +224,7 @@ Any user can be added or removed from a particular organization or a workspace a
227224

228225
The Teams feature provides a way for organizations to group various users and participants together into teams. For example, `workflow-developers` or `analysts`, and apply access control to all the users within this team collectively.
229226

230-
For further information, please refer to the [User Management](https://help.tower.nf/orgs-and-teams/organizations/) section.
227+
For further information, please refer to the [User Management](https://docs.seqera.io/platform/24.1/orgs-and-teams/organizations) section.
231228

232229
### Setting up a new organization
233230

0 commit comments

Comments
 (0)