Skip to content
Orchestra Platform

Contribute a Workshop

Want your workshop launchable in Orchestra? The journey is the same whether you start from a Bioconductor workshop package or an image you already have:

  1. Get a container. Either build a Bioconductor workshop package (which produces one for you) or bring an image you already publish.

  2. Make the image Orchestra-ready. Orchestra fronts every session with its own sign-in, so the app inside must start unauthenticated on a single port.

  3. Author a template. A small YAML file describes one catalog entry — image, port, resources, duration.

  4. Submit it. Fill in the issue form; a bot opens the PR after a maintainer approves. It appears in the catalog on the next deploy.

Start here

Section titled “Start here”
Build a Bioconductor workshop Use BuildABiocWorkshop to turn a workshop package into a container Orchestra can launch.
Bring your own container Already have a JupyterLab, RStudio, or custom image? Point a template straight at it.

Then

Section titled “Then”
Make the image Orchestra-ready The no-auth contract: start unauthenticated on one port, set via the template's port, env, and args.
Author a workshop template The field reference the issue form is built on — every catalog-entry field, and the fallback for hand-authors.
Submit it Fill in the issue form; a bot opens the PR after a maintainer approves.