Push Schema
Create the Config
To push a schema, it’s config must first be created. Navigate to the Configs page in the Miru dashboard.
Click + New Config
and name the config Mobility
with slug mobility
.
Config slugs are permanent and cannot be changed after creation.
Config Slugs
The config slug is a unique identifier for a config. It’s used by both the CLI and SDK to link a config schema to its corresponding config.
Thus all config schemas must include the $miru_config_slug
field at the root level. We’ve
already included this field in mobility.schema.yaml
.
Install the CLI
Schemas are pushed via the Miru command-line interface (CLI).
Run the installation command in your local machine’s terminal.
The script requires curl
, tar
, grep
, and cut
to be installed.
Review the contents of the installation script here.
The script requires curl
, tar
, grep
, and cut
to be installed.
Review the contents of the installation script here.
The Miru CLI supports macOS and Linux. Windows is not supported.
Login to the CLI
Run the login
command.
Retrieve your authentication token here.
Paste the token into the CLI.
Push to Miru
Navigate back to the root of the getting-started repository.
You’ll see a confirmation message that your schema was successfully pushed.
Visit the Configs page and click into the
Mobility
config to verify the schema was uploaded successfully.
Git information is pulled from the local git repository. If you don’t have access to view the remote repository (specified locally) or the commit hasn’t yet been pushed to the remote repository, git related links in Miru will be invalid.