Application Management (eda ls, info, set, rm)
Commands for inspecting running applications, listing inventory, updating resource quotas, and deleting services
Explita Deploy provides intuitive subcommands to manage the inventory, metadata, runtime quotas, and lifecycle of hosted applications.
1. List Applications (eda ls)
Display all registered applications on the remote server, including container status, assigned internal ports, custom domains, and latest deployment IDs.
eda ls [options]Options
| Flag | Shorthand | Type | Description | Default |
|---|---|---|---|---|
--search <query> | -s | String | Filter applications matching name, ID, or domain. | |
--page <n> | -p | Number | Page number for paginated results. | 1 |
--limit <n> | -l | Number | Number of applications displayed per page. | 5 |
Examples
# List all apps
eda ls
# Search for applications matching "api"
eda ls -s api
# View page 2 with 10 results per page
eda ls --page 2 --limit 102. Inspect Application (eda info)
Retrieve detailed telemetry, container states, resource allocations, attached domains, active tunnel status, and environment variable counts for an application.
eda info [options]Options
| Flag | Shorthand | Type | Description |
|---|---|---|---|
--app <appId> | -a | String | Target application ID (defaults to appId in local explita.json). |
Examples
# Inspect application bound to current working directory
eda info
# Inspect a specific remote application by ID
eda info -a app_9f3a12Output Fields:
- Application ID & Name: Unique identifier and human-readable label.
- Container State:
RUNNING,STARTING,STOPPED, orUNHEALTHY. - Resource Allocations: Current CPU quota (cores) and Memory limit (MB/GB).
- Network Routing: Internal container port, Caddy upstream targets, and registered custom domains.
- Active Release: Deployment ID, release tag (if set), and deployment timestamp.
- Environment: Number of configured encrypted environment variables.
3. Update Resource Quotas (eda set)
Update CPU and memory limits for an application's containers on the fly without requiring a rebuild or new git commit.
eda set [options]Options
| Flag | Shorthand | Type | Description | Example |
|---|---|---|---|---|
--app <appId> | -a | String | Target application ID. | -a app_9f3a12 |
--memory <mem> | String | Memory ceiling for the container. | --memory 1g | |
--cpus <cpus> | String | Maximum CPU cores allocated. | --cpus 1.5 | |
--subdomain <prefix> | -s | String | Set or update custom tunnel subdomain prefix. | -s staging-api |
--tunnel | -t | Boolean | Enable automated public HTTPS tunnel for the app. | -t |
--pre-deploy <cmd> | -P | String | Pre-deploy hook command before swapping traffic (repeatable). | -P "npx prisma migrate deploy" |
--volume <host:dest> | -v | String | Mount persistent Docker volume or host path (repeatable). | -v "/data:/app/data" |
-e, --env <KEY=VAL> | String | Set encrypted environment variable(s) (repeatable). | -e API_KEY=secret |
Examples
# Allocate 2GB RAM and 2 full CPU cores to the current app
eda set --memory 2g --cpus 2.0
# Set a 512MB memory limit on a background worker app
eda set -a app_worker_01 --memory 512mThe server updates Docker container resource quotas atomically using docker update and persists the settings in the database for future deployments.
4. Delete Application (eda rm)
Permanently delete an application and all its managed resources from the deployment server:
eda rm -a <appId> [options]Options
| Flag | Shorthand | Type | Description |
|---|---|---|---|
--app <appId> | -a | String | Target application ID to delete (required). |
--yes | -y | Boolean | Bypass interactive confirmation prompt. |
Examples
# Delete with interactive confirmation
eda rm -a app_9f3a12
# Delete non-interactively in CI/CD or automated teardown scripts
eda rm -a app_9f3a12 -yExecution Details:
- Server Teardown: Stops and force-removes all production, preview, and tunnel containers, deletes built release Docker images, purges source code directories on disk, drops associated databases and user roles, and flushes attached Redis database keys.
- Local Project Cleanup: If executed in a repository whose
explita.jsonis pinned to the target application (deploy.appId), the CLI automatically removesappIdwhile preserving your project settings (name,port,domains, etc.), preparing the repo for clean future deployments.
[!CAUTION] Application deletion is permanent and cannot be undone. All live containers, database records, deployment histories, and host disk assets are purged immediately. Remote backups previously archived to an external S3 bucket remain untouched in S3 for disaster recovery.