Apps

Apps represent individual applications within a project. Each app can have multiple releases and custom hostnames.

Overview

An app is a deployable application that:

• Belongs to a project
• Can have multiple releases (versions)
• Can have custom hostnames
• Maintains a current active release

Creating an App

Create a new app within your current project:

# Set project context first
brdz ctx:use

# Create the app
brdz apps:create my-app

The app name must be:

• Unique within the project
• URL-safe (lowercase letters, numbers, hyphens)
• Descriptive of the application

Example

# Create a web frontend app
brdz apps:create web-frontend

# Create an API app
brdz apps:create api

# Create a documentation site
brdz apps:create docs

Listing Apps

View all apps in your current project:

# List apps in current project
brdz apps:list

Output example:

ID    Name          Current Release    Created At
1     web-frontend  42                 2025-01-15 10:30:00
2     api           15                 2025-01-16 14:20:00
3     docs          8                  2025-01-17 09:15:00

Getting App Details

Get detailed information about a specific app:

brdz apps:get my-app

Output includes:

• App ID
• Name
• Current release ID
• Creation timestamp
• Project association

App Lifecycle

1. Create the App

brdz apps:create my-app

2. Set App Context

brdz ctx:use

3. Deploy Releases

brdz releases:create ./dist.zip

4. Add Custom Domains

brdz hostnames:create example.com

Working with Multiple Apps

Switching Between Apps

# Switch to a different app
brdz ctx:use

# Verify current app
brdz ctx:get

Deploying to Multiple Apps

# Deploy to first app
brdz ctx:use
brdz releases:create ./frontend.zip

# Deploy to second app
brdz ctx:use
brdz releases:create ./backend.zip

App Organization

Microservices Architecture

# Create separate apps for each service
brdz apps:create api-gateway
brdz apps:create user-service
brdz apps:create payment-service
brdz apps:create notification-service

Frontend and Backend

# Separate frontend and backend apps
brdz apps:create web-frontend
brdz apps:create api-backend

Multiple Environments

Within different projects, create matching apps:

# In production project
brdz ctx:use  # Select 'production'
brdz apps:create web-app

# In staging project
brdz ctx:use  # Select 'staging'
brdz apps:create web-app

Best Practices

1. Use descriptive names - Choose clear app names that indicate purpose
2. One app per service - Keep apps focused on single responsibilities
3. Set context before operations - Always verify ctx:get before deployments
4. Consistent naming - Use the same naming conventions across projects
5. Document purpose - Keep notes about what each app does

Limitations

• App names must be unique within a project
• Apps can only belong to one project
• App names cannot be changed after creation
• Deleting an app requires deleting all releases first

Commands Reference

apps:create <name>

Create a new app in the current project.

Requirements:

• Project context must be set

Arguments:

• name - App identifier (required)

Example:

brdz apps:create my-app

apps:list

List all apps in the current project.

Requirements:

• Project context must be set

Example:

brdz apps:list

apps:get <name>

Get detailed information about an app.

Requirements:

• Project context must be set

Arguments:

• name - App identifier (required)

Example:

brdz apps:get my-app

Related Topics

• Projects - Creating projects to contain apps
• Releases - Deploying releases to apps
• Hostnames - Adding custom domains to apps
• Context Management - Managing app context
• Core Concepts: Apps - Understanding app architecture

See Also

• Deploy Your First App
• Quick Start Guide