shc repoint
shc repoint
Section titled “shc repoint”move a deployment’s recorded source onto a catalogue app or a git remote (renders nothing)
Synopsis
Section titled “Synopsis”Move a deployment’s recorded source from an import path onto a catalogue
app, so it can resolve published versions and appear in shc catalog updates, or onto a git remote at a ref, so later updates render that
remote instead of the path.
A deployment installed from a local path keeps that path as its app name
forever. Both halves of its drift check then resolve to the same
directory, so shc update --check reports current no matter how far the
catalogue has moved. Repointing the row is what lets the two disagree.
It renders nothing. No container is created, destroyed or restarted, and
no data is touched. Converging is the next shc update, which stays a
deliberate step. Read --diff first, and for a deployment holding live
data take a backup and a window before you run it.
The deployment’s --var overrides, integrations, routes, ports and quotas are untouched: a repoint rewrites which app the next update reads, and nothing else.
A git target takes --ref and --path as install does. --token reads a private remote for this repoint only and is never recorded: a later update reads the remote with a node credential or its own --token.
shc repoint <stack> [[<repo>/]<app>[@<version>] | <git-url>[#<ref>:<path>]] [flags]Examples
Section titled “Examples” shc repoint supabase supabase --diff shc repoint supabase [email protected]+32 -t corp -e prod shc repoint photos immich -r apps shc repoint photos apps/immich shc repoint pokemon-kc https://git.example.com/acme/product.git --ref <sha> --path deploy/shc/keycloak --diff shc repoint supabase --backOptions
Section titled “Options” --back return the deployment to the source the last repoint moved it off --diff report what the next update would change and write nothing -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") -h, --help help for repoint --path string subdirectory of a git target that holds the app --ref string git reference a git target renders from -r, --repo string resolve the catalogue app from this repository (overrides repo priority) -t, --tenant string tenant name --token string authentication token for a private git target, used for this repoint onlyOptions 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) --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) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc - Selfhosted Cloud CLI