shc catalog compile
shc catalog compile
Section titled “shc catalog compile”compile one catalog application into the exact install invocations
Synopsis
Section titled “Synopsis”The tile is a compiler: catalog compile returns the shc install
commands a tile for the application would emit (exact pin, prerequisite
host, target) and you execute them. It installs nothing.
shc catalog compile <application> [flags]Options
Section titled “Options” --addon string addon to apply (typed: app addons on apps, vaddons on vapps) --addon-version string addon version key or alias (default: the addon's own default) -h, --help help for compile --instance string instance name for a vdeployment -i, --integrate strings integration selection as plug=target; passthrough, the catalog never picks a target --into string deployment a vdeployment attaches to --repo string qualify the application when two repositories publish itOptions inherited from parent commands
Section titled “Options inherited from parent commands” --config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win -d, --debug enable debug mode (default: $SHC_DEBUG) -e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default") --exclude string comma-separated dotted paths to drop --fields string comma-separated columns/keys to show (and their order) --filter string comma-separated dotted paths to keep (drops everything else) -o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT) -s, --stack string stack name (default: $SHC_STACK) -t, --tenant string tenant name (default: $SHC_TENANT) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc catalog - browse what the registered repositories publish
shc@docs:~$