|
1 | 1 | --- |
2 | | -title: How-to Guide landing page template |
3 | | -type: template |
4 | | -contributors: |
5 | | -description: Add a plain text description here. |
6 | | -affiliations: |
| 2 | +title: BioShell |
| 3 | +description: A guide to accessing and using BioShell, a preconfigured cloud bioinformatics |
| 4 | + environment available on NCI Nirin and ARDC Nectar Research Cloud. |
7 | 5 | sidebar: false |
8 | 6 | --- |
9 | 7 |
|
| 8 | +## Introduction |
10 | 9 |
|
11 | | -**Replace the text below with your guide content!** |
| 10 | +BioShell is a ready-to-use cloud bioinformatics environment designed to get you from data to |
| 11 | +results with as little setup as possible. Rather than spending time configuring software on |
| 12 | +your own machine, you connect to BioShell and find a fully equipped workspace already waiting |
| 13 | +for you — with the tools, compute power, and interactive environments you need to run analyses |
| 14 | +that would be impractical on a laptop. |
12 | 15 |
|
13 | | -Example templates that you could use for different guides are available in this repository: |
| 16 | +BioShell is available through NCI Nirin and ARDC Nectar Research Cloud and is designed for |
| 17 | +researchers and learners at all stages. Whether you are a higher degree student running your |
| 18 | +first bioinformatics analysis, a trainer delivering a national workshop, or a researcher who |
| 19 | +needs a consistent and reproducible environment to share with collaborators, BioShell removes |
| 20 | +the technical overhead so you can focus on your science. |
14 | 21 |
|
15 | | -- [Standard page that can be used as a starting point for any type of guide.](example_page) |
16 | | -- [Suggested structure for a guide describing how to use a bioinformatics workflow](example_bioinformatics_workflow_page) |
17 | | -- [Suggested structure for documentation describing a workflow: based on Australian BioCommons documentation guidelines](example_workflow_documentation_page) |
| 22 | +This guide walks you through requesting access, choosing the right environment for your work, |
| 23 | +and using BioShell's built-in tools and support features. It assumes you are comfortable |
| 24 | +with basic command-line navigation, but no prior experience with cloud infrastructure, |
| 25 | +containers, or software installation is needed. BioShell is developed by Australian BioCommons |
| 26 | +as part of the [ABLeS programme](https://australianbiocommons.github.io/ables/) and supports |
| 27 | +the BioCommons Training cooperative and |
| 28 | +[Bioinformatics ToolFinder](https://australianbiocommons.github.io/2_tools.html). |
18 | 29 |
|
19 | | -Use cases for different guides are described in the [How-to Guide for using this template](https://australianbiocommons.github.io/how-to-guide-template/how_to_guide_types). |
| 30 | +> **Note:** This guide does not cover how to provision a virtual machine on Nectar or NCI, or |
| 31 | +> how to build a BioShell instance from scratch. See the |
| 32 | +> [BioShell GitHub repository](https://github.com/AustralianBioCommons/BioShell) and the |
| 33 | +> infrastructure documentation for those topics. |
| 34 | +
|
| 35 | +--- |
| 36 | + |
| 37 | +## Quick start guide |
| 38 | + |
| 39 | +1. [Check you are eligible](/access#eligibility) — confirm your project is life-science |
| 40 | + related and aligns with the five ABLeS principles. |
| 41 | +2. [Identify your access pathway](/access#pathways) — most users apply through |
| 42 | + [ABLeS](https://australianbiocommons.github.io/ables/eligibility); training organisers |
| 43 | + contact the [BioCommons Training Team](https://www.biocommons.org.au/event-support). |
| 44 | +3. [Submit your access request](/access#requesting-access) — submit via the appropriate |
| 45 | + pathway and wait for your infrastructure placement to be confirmed. |
| 46 | +4. [Accept your terms and conditions](/access#terms) — accept the terms for your assigned |
| 47 | + infrastructure before access is granted. |
| 48 | +5. [Connect to your BioShell environment via SSH](/access#connecting) — use the connection |
| 49 | + details provided in your provisioning notification. |
| 50 | +6. [Choose your flavour](/using-bioshell#flavours) — select the preconfigured environment |
| 51 | + profile that matches your task. |
| 52 | +7. [Load a tool and run your analysis](/using-bioshell#tools) — use Bio-Shelley or |
| 53 | + `module load` to access tools from the BioShell tool library. |
| 54 | +8. [Launch an interactive environment](/using-bioshell#interactive) — open JupyterLab or |
| 55 | + RStudio directly in your browser for notebook-based work. |
| 56 | + |
| 57 | +> **Tip:** Not sure which tools are available or how to load them? Run |
| 58 | +> `shelley-bio search "<what you want to do>"` for instant suggestions. |
| 59 | +
|
| 60 | +--- |
| 61 | + |
| 62 | +## How to cite |
| 63 | + |
| 64 | +If you use BioShell in your research or training, please cite it as: |
| 65 | + |
| 66 | +> O'Brien M, Jaya F, Samaha G, Xue W, Al Bkhetan Z, Botting A, Gustafsson J. (2026). |
| 67 | +> **BioShell how-to guide**. Australian BioCommons. |
| 68 | +> [AUTHOR TO SUPPLY — Zenodo DOI once minted] |
| 69 | +
|
| 70 | +--- |
| 71 | + |
| 72 | + |
| 73 | + |
| 74 | +*Fig 1. Overview of the BioShell access and use flow: from submitting an access request |
| 75 | +through to connecting, choosing a flavour, loading tools, and launching interactive |
| 76 | +environments.* |
0 commit comments