CLI Guides
Master the Aevum Zenth command-line interface for deployment, configuration, and infrastructure management.
Installation
The Aevum Zenth CLI is available for macOS, Linux, and Windows. Choose your package manager or OS below:
# Using Homebrew (recommended) brew tap aevum-zenth/tap brew install aevum # Verify installation aevum --version
# Using apt (Debian/Ubuntu) curl -fsSL https://cli.aevum-zenth.com/apt/gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/aevum-zenth.gpg echo "deb [signed-by=/usr/share/keyrings/aevum-zenth.gpg] https://cli.aevum-zenth.com/apt stable main" | sudo tee /etc/apt/sources.list.d/aevum-zenth.list sudo apt update sudo apt install aevum-cli
# Using winget winget install AevumZenth.AevumCLI # Using Chocolatey choco install aevum-cli
Requires Node.js 18+ (for extensions), Git 2.30+, and a valid Aevum Zenth account. The CLI automatically handles dependency resolution.
Authentication
Secure your CLI sessions using OAuth2 tokens or API keys. Sessions persist in ~/.aevum-zenth/credentials.
# Interactive browser login (recommended) aevum auth login # Service account token aevum auth token --key $AEVUM_TOKEN # Verify current session aevum auth whoami # → user: dev-team@aevum-zenth.com | org: enterprise-01 | role: admin
For CI/CD pipelines, set the AEVUM_CLI_TOKEN environment variable. The CLI will automatically prioritize it over local credentials.
Project Initialization
Scaffold a new Aevum-managed project with infrastructure templates, CI configs, and best practices.
aevum init my-app \ --template react-monorepo \ --region us-east-1 \ --env production
This creates a standard directory structure with pre-configured Infrafile.yaml, GitHub Actions workflows, and environment scaffolding.
Deployment
Push code to Aevum's edge network with zero-downtime canary or blue-green strategies.
| Command | Description |
|---|---|
aevum deploy | Push current branch to production |
aevum deploy --staging | Deploy to staging environment |
aevum deploy --dry-run | Validate config without pushing |
aevum deploy --rollback | Revert to previous stable release |
Deployments to production require --confirm or CONFIRM_DEPLOY=true in CI. Rollbacks are automatic if health checks fail within 60s.
Logging & Monitoring
Stream real-time logs, filter by severity, and trace distributed requests across your infrastructure.
# Stream production logs aevum logs --env production --follow # Filter by severity & service aevum logs --level error --service auth-service # Trace a specific request ID aevum trace req_8x92a1b4c3 --format json
Configuration
The CLI reads from ~/.aevum-zenth/config.yaml. Override defaults with flags or environment variables.
cli:
default_region: eu-west-1
auto_update: true
telemetry: false
log_level: warn
profiles:
development:
org_id: org_dev_99
env: dev
production:
org_id: org_prod_01
env: prod
confirm_deploy: trueaevum doctor
Run diagnostics to verify installation, connectivity, permissions, and quota limits.
aevum doctor ✅ CLI version matches server ✅ Authentication valid (expires in 14h) ✅ Network latency: 42ms ⚠️ Disk space: 12% free (threshold: 20%) Run `aevum cache clean` to reclaim 4.2GB
Verbose Mode & Debugging
Enable verbose output for debugging failed commands, network issues, or config mismatches.
# Single command aevum deploy --verbose # Global verbose mode aevum config set cli.log_level debug # Output raw HTTP requests/responses AEVUM_DEBUG=true aevum auth login
Verbose mode may expose tokens or PII in logs. Never run --verbose in shared environments or production CI.