Pull into a project

Add a product's current release to your project, safely and without overwriting anything.

orvio pull downloads a product's current release and writes its files into a folder. It checks the download first, and it never overwrites a file you already have.

Steps#

1. 1

   Find the product

   TerminalCopy

   $ orvio search pricing
   

2. 2

   Look at what is in it

   TerminalCopy

   $ orvio info sotto
   

3. 3

   Pull it

   TerminalCopy

   $ orvio pull sotto
   

   By default the files go into ./sotto. Give a path to choose another folder:

   TerminalCopy

   $ orvio pull sotto ./my-app
   

What is checked, and when#

1. The CLI asks Orvio for the release. Orvio checks your membership.
2. The CLI downloads the ZIP. The download's size and SHA-256 must match what Orvio announced.
3. Every entry of the ZIP is checked before anything is written.
4. Then files are written. A mismatch writes nothing and exits with code 2.

What is never overwritten#

An existing file, folder or link is never replaced. The CLI skips it and lists it. An entry that would land outside the target folder, or that goes through a symbolic link, is refused.

$ orvio pull fixture-studio
Skipped 4 files (nothing was overwritten):
  orvio.json (already exists)
  source/css/site.css (already exists)
  source/index.html (already exists)
  source/js/main.js (already exists)
Added 0 files from Fixture Studio 1.2.0 to ./fixture-studio. Your framework and existing files were kept.

That output is real: it is the second run of the same pull, from the CLI's tests with a synthetic product.

What lands in the folder#

The whole release, as authored: the product's source/ folder and the Orvio package around it. See What's in a release.

Only the latest release#

You cannot pull an older version. Naming one answers release_replaced.

Use the files#

Point your agent at the folder and use the prompts of the Prompt library without "Using Orvio". Read the licence first: The licence in practice.