BST-PULL(1)

πŸ’– BST PULL(1) πŸ’–

okay bestie, welcome to the bst pull manual page, straight out of the bst pull Manual ✨


🌸 NAME 🌸

bst-pull β€” pull a built artifact 🫢


✨ SYNOPSIS ✨

bst pull [OPTIONS] [ELEMENTS]...

πŸ¦‹ DESCRIPTION πŸ¦‹

So basically, bst pull grabs a built artifact from the configured remote artifact cache. it's giving "go get my stuff" energy πŸ’…

By default, the artifact gets pulled from one of the configured caches if possible, and it follows the usual priority order β€” the caches know their lineup, periodt. but if you pass the --remote flag, then only the specified cache will be queried. no backups, no plan B, just that one. iconic but also lowkey commitment πŸ’€

If you wanna control which artifacts get pulled, specify --deps. here's the vibe check:

  • none: No dependencies, just the element itself πŸŽ€
  • all: All dependencies 🌈

πŸ‘‘ OPTIONS πŸ‘‘

  • -d, --deps [none|all] β€” The dependency artifacts to pull (default: none). so like, if you don't say anything, it's just the element itself, no entourage 🧚
  • -r, --remote TEXT β€” The URL of the remote cache (defaults to the first configured cache). leave it blank and it'll just go with whoever's first in line πŸ’–

and that's the whole page, bestie, you ate that πŸ’…βœ¨

this lil slice of documentation came from the bst pull Manual and it's dated 14-Jul-2019 β€” stay slay, keep pulling those artifacts, mwah πŸŽ€πŸ¦‹πŸ’œ