Skip to content

update guides #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ziadbkh merged 1 commit into from
Aug 24, 2025
Merged

update guides #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added assets/doc_img/token.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
9 changes: 7 additions & 2 deletions user-guide/compute-env.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,12 @@ The following steps need to be completed in order unless they have been complete
<div class="accordion-body">
You don’t need an access token if you intend to create SSH key credentials, but you will need it for the Tower Agent credentials.
<ul>
<li>The user can create an access token as <a href="https://docs.seqera.io/platform/latest/api/overview/?h=access+token#authentication"> described here</a>.</li>
<li>Navigate to the <code>User Tokens</code> from the user menu on the top-right corner:
<br/>
<div style="text-align:center"><img width="25%" src="../assets/doc_img/token.png"/></div>
<br/>
</li>
<li>Click <code>Add Token</code> and give the token a name.</li>
<li>Keep it safe, create a new one if you lose it and delete lost tokens.</li>
<li>Use descriptive names.</li>
<li>Don’t share your token with others.</li>
Expand Down Expand Up @@ -88,7 +93,7 @@ The following steps need to be completed in order unless they have been complete
<ol>
<li>Keep the Agent interface open.</li>
<li>Log in to infrastructure (the HPC).</li>
<li>In theory, you can run the Agent from anywhere on the HPC. See our [best practices](/user-guide/hpc-recommendations) for some recommendations.</li>
<li>In theory, you can run the Agent from anywhere on the HPC. See our <a href="/user-guide/hpc-recommendations">best practices</a> for some recommendations.</li>
<li>Copy the usage script from the Agent interface to any text editor and edit the access token to provide your own token created above and provide the path to the work directory for the Agent.</li>
<li>The work directory for the Agent (provided as a parameter in the command) must exist before running the Agent.</li>
<li>Run the edited script relevant to your infrastructure (PBS or SLURM) bash.</li>
Expand Down
Loading