gws profile

List the configuration profiles defined under profiles.* in gws.json. Profiles let you keep environment-specific overrides (CI, staging, minimal-dev, …) in the same gws.json instead of maintaining parallel files. Most commands accept --profile <name> to apply one.

For the full profile model — what fields can be overridden, merge semantics — see Configuration Profiles in the developer-internal docs.

Usage

gws profile

No arguments, no options. Reads gws.json from the current directory.

Auth: requires gws.json.

Output

📋 Available profiles:

  ci         Minimal services for CI
  staging    Staging-cluster overrides
  minimal    Frontend-only profile

💡 Usage: gws up --profile <name>

If no profiles section exists in gws.json:

No profiles defined in gws.json

When run with the global -v / --verbose flag (wired by every command via the Commander base class — gws profile itself defines no options), the output also lists which top-level keys each profile overrides — registry, services (with count), provision.environments.

Examples

# List profiles
gws profile

# List with override details (global verbose flag)
gws profile --verbose

# Use a profile (only commands that accept --profile do this — currently `gws up`)
gws up --profile ci

Usage​

Output​

Examples​

See also​

Usage

Output

Examples

See also