Skip to main content
Version: v5.7.0

opschain config

Included from Basic tier

Print the effective client configuration — the one answer to "what would an opschain command here actually use":

  • Home — the resolved opschain home (--home, OPSCHAIN_HOME, or the per-OS data directory).
  • Context — the resolved execution target: a named context, local, or (ad-hoc flag) / (ad-hoc env) when --server or OPSCHAIN_SERVER targets a server no context names. The Server line appears for remote targets.
  • Project — the parsed .opschain/config.yaml of the current repository: project code, environments (with their assets), and the properties root. The file is validated against the frozen project-config schema before printing; an invalid file is an error, a missing one prints Project: none with a pointer to opschain init.
opschain config
Home:         /home/op/.local/share/opschain
Context:      local
Config file:  /work/demo/.opschain/config.yaml
Project:      demo
Environment:  dev (assets: web, db)
Properties:   .opschain/properties

-o json|yaml emits the same as one document (home, context, server, config_file, project_config). This is a read-only, local command — the server is never contacted. There are no local flags.

Exit codes: 0 on success, 1 when .opschain/config.yaml exists but is invalid or unreadable, 2 for a usage error (including the global --local and --server are mutually exclusive refusal).

See also​

  • opschain docs cli/init — scaffold the project config this command prints.
  • opschain docs cli/context — just the target-resolution half.