Created by potrace 1.16, written by Peter Selinger 2001-2019

Miva Developer Docs


A remote is a saved combination of a credential, a store code and a branch name, under a name you choose. mmt checkout and mmt switch use it. Remotes are stored in your user profile (~/.mmt/config.json), not in a checkout, so one remote can serve many checkouts.

mmt remote list#

Lists your remotes.

mmt remote list

This command takes no arguments.

mmt remote add#

Adds a remote. The store and branch aren’t checked until you use the remote.

mmt remote add --credential-key CREDENTIAL_KEY --branch-name BRANCH_NAME --store-code STORE_CODE key
Argument Short Required Description
--credential-key CREDENTIAL_KEY -c Yes The key associated with the stored credential.
--branch-name BRANCH_NAME -b Yes The branch name to checkout.
--store-code STORE_CODE -s Yes The store code from which to checkout.
key Yes A name for this remote. checkout and switch refer to it by this name.

Example:

mmt remote add -c mystore -s ST -b Development mystore-dev

mmt remote update#

Changes the fields you give.

mmt remote update [--remote-key REMOTE_KEY] [--credential-key CREDENTIAL_KEY] [--store-code STORE_CODE] [--branch-name BRANCH_NAME] key
Argument Short Required Description
--remote-key REMOTE_KEY -r No Rename the remote. Checkouts that use the old name aren’t updated.
--credential-key CREDENTIAL_KEY -c No The key associated with the stored credential.
--store-code STORE_CODE -s No The store code associated with the remote resource.
--branch-name BRANCH_NAME -b No The branch name associated with the remote resource.
key Yes The remote to change.

mmt remote delete#

Deletes one or more remotes.

mmt remote delete key [key ...]
Argument Short Required Description
key ... Yes One or more remotes to delete.

Renaming or deleting a remote doesn’t update checkouts that use it. Those checkouts then fail with MMT-COMMAND-00010; run mmt switch in them with the new name.