Clients

TL;DR on Installing elv

Default install to ${HOME}/bin

curl -s https://docs.eluv.io/installer/elv.sh | bash -s

Install to /usr/local/bin with elevated/root permissions

curl -s https://docs.eluv.io/installer/elv.sh | sudo bash -s -- -e

Install to an alternate directory ${SOME_DIR} as a normal user

curl -s https://docs.eluv.io/installer/elv.sh | bash -s -- -p ${SOME_DIR}

Help/Usage message

curl -s https://docs.eluv.io/installer/elv.sh | bash -s -- -h

Introduction

Eluvio’s Content Fabric is implemented in an application called qfab. The qfab daemon, along-side elvmasterd effectively create the Content Fabric. To operate on the Content Fabric, the CLI tool qfab_cli is normally used, but it is usually built with dependencies that most people don’t use. Eluvio builds a stripped version of this called elv. When elv is installed, it can interact with parts, inspect the spaces, etc. It is available on a number of different platforms.

Customizing the Installation

To get the latest version of the usage for the installer, us -h:

curl -s https://docs.eluv.io/installer/elv.sh | bash -s -- -h

The options that you will see available are:

  • -h, --help: The usage dialog
  • -x, --do-not-verify: Don’t verify install. It will not run elv -v, which can be useful
  • -p <path>, --install-path <path>: Set install path base (before bin)1
  • -e, --elevated-install: Installing with elevated priveledges2

  1. This directory needs to be before bin. If you plan to install to /usr/local/bin, then use -p /usr/local. ↩︎

  2. Elevated (run as root) install defaults to -p /usr/local. It is alright to also specify -p ↩︎

OS NOTES