eda configCopy Anchor Link

The eda config command group manages local workstation settings and project bindings for Explita Deploy. Configuration is split into global user settings (~/.explita/config.json) and project-level settings (explita.json).

eda config [subcommand]
explita deploy config [subcommand]

1. Subcommands OverviewCopy Anchor Link

2. Supported Configuration KeysCopy Anchor Link

3. Usage ExamplesCopy Anchor Link

# View all active settings
eda config ls

# Set remote server address
eda config set server http://198.51.100.42:39756

# Set host authentication token
eda config set token sec_your_deploy_token_here

# Query specific setting
eda config get server

# Show paths to configuration files on disk
eda config path

4. Zero-Disk Passcode Security BoundaryCopy Anchor Link

[!IMPORTANT] Passcodes and PINs are strictly prohibited from configuration files. To preserve the security boundary of secondary authentication, passcodes (DEPLOY_PASSCODE) are never stored in configuration files (they are known strictly to the human operator in memory).

If a server enforces passcode authentication:

1. In interactive terminals, eda prompts:

   Copy Text

   🔑 Enter deploy passcode / PIN:

2. In non-interactive CI/CD scripts or commands, supply it inline in memory:

   Copy Text

   eda promote d79 --pass secret-pin-9876

The passcode is never written to disk, so compromised workstations or leaked repositories will not expose the host.