Filerobot CLI for programmatic management of your DAM library

The Filerobot CLI allows the management of the Filerobot media asset library via simple commands on macOS or Linux. The following features are available:

  • single and batch asset upload
  • single and batch asset download
  • single and batch asset delete
  • list
  • obtain asset information like metadata, tags and various links
  • move assets from one folder to another
  • rename assets

The full documentation is available on GitHub; below is a quick start:

Installation

macOS

sudo curl -L "https://github.com/scaleflex/filerobot-cli/releases/download/1.0/filerobot-cli-darwin-x86_64" 
-o /usr/local/bin/filerobot && sudo chmod +x /usr/local/bin/filerobot

Linux

sudo curl -L "https://github.com/scaleflex/filerobot-cli/releases/download/1.0/filerobot-cli-linux-x86_64" 
-o /usr/local/bin/filerobot && sudo chmod +x /usr/local/bin/filerobot

To validate the installation of the CLI, run:

filerobot version 


Configuration

Configuring the CLI requires a Filerobot Token (Token) and API Secret Key (APISecretKey), both available from the Filerobot Asset Hub.

filerobot config --token=Token --key=APISecretKey

mceclip2.png

mceclip1.png

Upload

To upload your first file via the CLI, run the following command:

filerobot upload face.png

Where face.png is an asset on your local machine.

You can also upload into a specific folder:

filerobot upload face.png --folder=/Marketing

The folder will be created if it does not exist.

The command returns the status and 2 links to the asset:

SUCCESS: Uploaded successfully in 1.288758425s,
CDN - https://ficttndm.filerobot.com/CLI/IMG_2002.jpg?vh=4e80bf
Public - https://store.filerobot.com/ficttndm/CLI/IMG_2002.jpg

The first link is a CDN link supporting media transformations, the second one is the direct link to the Filerobot Store.

Help

All available commands are available via:

filerobot --help

The full documentation is available on Github.

If you have any questions or issues, please feel free to contact our Software Engineer and mention the following details:

  • Token
  • Short description of the issue (including URLs, screenshots, short video if available)
  • Steps to reproduce the issue.
Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.