Context Management

Context management allows you to set your working project and app once, then run commands without repeatedly specifying them.

Understanding Context

The brdz CLI maintains a context that includes:

Current project - The project you’re working with
Current app - The app within that project

Once set, commands that require a project or app will use your context automatically.

Setting Context

Use the interactive context selector:

brdz ctx:use

This command will:

Show a list of your projects
Prompt you to select a project
Show apps in that project (if any)
Prompt you to select an app
Save your selection to ~/.brdz/context

Viewing Current Context

Check your current context:

brdz ctx:get

Output example:

Project: my-project
App: my-app

Context Storage

Your context is stored in ~/.brdz/context:

~/.brdz/
├── credentials    # API key and hostname
└── context        # Current project/app context

Overriding Context

You can override the saved context using environment variables:

# Override project
export BRDZ_PROJECT="different-project"

# Override app
export BRDZ_APP="different-app"

# Run commands with overridden context
brdz apps:list

Context-Aware Commands

These commands use your current context:

Requires Project Context

apps:create - Creates app in current project
apps:list - Lists apps in current project
apps:get - Gets app from current project

Requires App Context

releases:create - Creates release for current app
releases:list - Lists releases for current app
releases:rollback - Rollbacks current app
hostnames:create - Adds hostname to current app
hostnames:list - Lists hostnames for current app

Workflow Examples

Initial Setup

# Create and select a project
brdz projects:create my-project
brdz ctx:use

# Create and select an app
brdz apps:create my-app
brdz ctx:use

# Now deploy without specifying project/app
brdz releases:create ./dist.zip

Switching Between Projects

# Switch to a different project and app
brdz ctx:use

# All subsequent commands use the new context
brdz apps:list
brdz releases:list

Working with Multiple Apps

# Set context to first app
brdz ctx:use

# Deploy to first app
brdz releases:create ./app1.zip

# Switch to second app
brdz ctx:use

# Deploy to second app
brdz releases:create ./app2.zip

Context in CI/CD

For automated deployments, use environment variables instead of interactive context:

# Set context via environment
export BRDZ_PROJECT="production"
export BRDZ_APP="web-app"

# Deploy without interactive prompts
brdz releases:create ./dist.zip

Best Practices

Set context early - Run ctx:use after creating projects and apps
Verify context - Use ctx:get before critical operations
Use environment variables in automation - Don’t rely on file-based context in CI/CD
Update context when switching work - Change context when working on different projects

Troubleshooting

”No project in context” Error

If you see this error:

Run brdz ctx:use to set your project
Verify your project exists: brdz projects:list
Check environment variables aren’t empty

”No app in context” Error