omm

omm export

Export a hub model to `destination` for deployment or backup: a hard link when possible, otherwise a real copy. Never a symlink, so the exported file keeps working after `omm uninstall` or on another machine. Not tracked in the registry - uninstalling the source model never touches an exported copy. Also writes a provenance/checksum manifest sidecar next to it, so `omm import` on another machine (including an air-gapped one) can restore the source repo, version, and install date instead of treating the file as an anonymous import.

Exactly what omm export --help prints, exported from the CLI source.

Usage

omm export [OPTIONS] {filename} {destination}

Arguments

  • filenamerequired

    —

  • destinationrequired

    Directory to place the exported file in.

Options

  • --forceDefault: —

    Reclaim a destination omm doesn't recognize as its own by deleting it and exporting, instead of skipping it as a conflict.

Shared flags

Every omm command also accepts --json, --no-color, --quiet, -q, --yes, -y, so they are listed here once instead of on each command.

Exported from omm 0.3.101.

All commands