Remote Execution (eda sh, eda exec)

Explita Deploy provides secure remote execution primitives that tunnel standard input/output (TTY) directly into your running containers over an authenticated WebSocket connection. Developers can run administrative commands, database migrations, and debugging shells without needing host SSH keys or root server access.

eda sh [options]
eda exec [options] -- <command...>

1. Interactive Terminal Shell (eda sh)Copy Anchor Link

Attach an interactive TTY shell session inside the live container:

eda sh [-a <appId>] [-s <shell>]
# Aliases: eda shell, eda exec -it

OptionsCopy Anchor Link

ExamplesCopy Anchor Link

# Open interactive shell in current app
eda sh

# Specify bash shell explicitly
eda sh -s bash

# Open shell in specific remote application
eda sh -a app_9f3a12

2. One-Off Command Execution (eda exec)Copy Anchor Link

Run a single non-interactive command inside the container environment and stream the exit code and output back to your terminal:

eda exec [-a <appId>] -- <command...>
# Alias: eda run

ExamplesCopy Anchor Link

# Run database schema migrations
eda exec -- npx prisma migrate deploy

# Run Django database migrations
eda exec -- python manage.py migrate

# Execute a one-off database seed script
eda exec -- node dist/scripts/seed.js

# Check disk space inside the container
eda exec -- df -h

3. Security & IsolationCopy Anchor Link

• Non-Privileged User: Commands execute with the user designated in your Dockerfile (USER node, USER app, etc.).
• Encrypted Variables Available: All runtime environment variables configured with eda env set are available to the process.
• Audit Logging: All eda exec invocations and shell session connections are recorded in server audit logs with timestamp and token signature.