For the complete documentation index, see llms.txt. This page is also available as Markdown.

Command Line Interface

Manage automations, scripts, run tests, view logs, download, watch, publish and more from the command line.

Commands

Type mesa to get a list of available commands:

mesa export
mesa push [params]
mesa pull [params]
mesa watch
mesa install [version]
mesa test
mesa replay mesa logs [-v] [-n 50]

Optional Parameters:
-e, --env [value] : Environment to use (filename in ./config/).
-a, --automation [value] : Automation key. Automatically determined by the mesa.json file if not specified.
-f, --force : Force, overwrite config for inputs/outputs/storage.
-n, --number [value] : Number.
-v, --verbose : Verbose: Show log metadata.

Installing

With yarn

Or with NPM

Upgrading

To upgrade to the latest version

Configuring sites

Create a new directory with a config.yml file:

The config.yml file can be in your current working directory, or in ~/.mesa/config.yml so you can run mesa from any working directory.

uuid is your myshopify.com subdomain: UUID.myshopify.com key is your site's MESA Key from the bottom of the Reports tab of the MESA Dashboard . Optional parameter: api_url.

Specifying environments

  • Delete your global ~/.mesa/config.yml file

  • Save configuration files in ~/.mesa/config. For example: ~/.mesa/config/mystoreuuid.yml

  • Pass the environment with the --env or -e flags, or by setting the ENV envvar:

Full details on usage

Editing Automations

To get started, export an automation to download the scripts and configuration into the current directory:

Then use the utility functions to keep your local code in sync with MESA:

<...files> can be:

Specific path(s) to files: tracktor/in-webhook.js tracktor/out-webhook.js

Or for multiple files: tracktor/*

Local development

To clone mesa-cli locally and install it globally:

Last updated