Manage Crates

Bulker stores crate manifests in a local cache. The crate subcommands let you see what is cached, inspect what commands a crate exposes, and remove crates you no longer need.

List cached crates

Use bulker crate list to see every crate currently in your local cache:

$ bulker crate list
bulker/demo:default
bulker/cutadapt:0.1
bulker/bowtie2:default

To include all installed tags for each crate, pass --versions:

$ bulker crate list --versions
bulker/demo:default
bulker/demo:0.3
bulker/cutadapt:0.1

For scripting or shell completion use, the --simple flag prints a flat space-separated list:

$ bulker crate list --simple
bulker/demo:default bulker/cutadapt:0.1 bulker/bowtie2:default

Inspect a crate

Once you know which crates are cached (or even if the crate is not yet cached), use bulker crate inspect to see the commands it exposes:

$ bulker crate inspect bulker/demo
Commands: fortune, cowsay

You can inspect any crate by its registry path, whether or not it is currently active.

You can also check which crate is currently active by looking at the $BULKERCRATE environment variable:

echo $BULKERCRATE

Remove cached crates

Use bulker crate clean to remove a specific crate from the local cache:

$ bulker crate clean bulker/demo:default

This removes the cached manifest for that crate. The next time you activate it, bulker will re-fetch the manifest from the registry.

To clear the entire crate cache at once, pass --all:

$ bulker crate clean --all

Use --all when you want to start fresh or reclaim disk space. Any crate you activate afterwards will be re-fetched automatically.