DanubeData CLI

The DanubeData CLI (danube) lets you manage your entire DanubeData infrastructure from the terminal — VPS instances, object storage, static sites, and serverless containers. Built with Node.js, it provides interactive prompts, real-time build tracking, and CI/CD-friendly configuration.

Installation

Requires Node.js 18 or later.

npm install -g @danubedata/cli

Verify the installation:

danube --version

Authentication

Browser auth (recommended)

danube auth

Opens your browser to log in and authorize the CLI automatically — no manual token copying.

Interactive login

danube login

You will be prompted to enter your API token. To create a token:

1. Log in to the DanubeData dashboard
2. Go to Settings > API Tokens
3. Click Create New Token and copy the token

Token flag

danube login --token YOUR_API_TOKEN

Environment variable

Set the DANUBE_TOKEN environment variable to skip the login step entirely. This is the recommended method for CI/CD pipelines.

export DANUBE_TOKEN="your-api-token"

Check your identity

danube whoami

Shows your name, email, and team memberships.

Log out

danube logout

Removes stored credentials from ~/.danube/config.json.

Configuration

Credentials

Stored at ~/.danube/config.json with 0600 permissions:

{
  "token": "your-api-token"
}

Project configuration

Created by danube pages link, stored at .danube/project.json:

{
  "siteId": 42,
  "teamId": 1,
  "siteName": "my-portfolio",
  "defaultDomain": "my-portfolio-abc.pages.danubedata.ro"
}

Build configuration

Optional danube.json in your project root:

{
  "outputDir": "dist",
  "ignore": ["*.map", "test/**"]
}

• outputDir — Directory to deploy (default: current directory)
• ignore — Additional file patterns to exclude from the deployment

Environment variables

Commands overview

General

VPS Instances (danube vps)

Object Storage (danube storage)

Static Sites (danube pages)

Serverless Containers (danube rapids)

File exclusion

When packaging files for deployment, the CLI automatically excludes:

1. .git, node_modules, .danube (always excluded)
2. Patterns from .gitignore
3. Patterns from .daubeignore (custom ignore file)
4. Extra patterns from danube.json ignore field

CI/CD usage

For automated deployments without interactive prompts, set environment variables:

export DANUBE_TOKEN="your-api-token"
export DANUBE_SITE_ID="42"
export DANUBE_TEAM_ID="1"

danube pages deploy --dir ./dist --no-wait

GitHub Actions example

name: Deploy to DanubeData
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: 20

      - run: npm ci && npm run build

      - run: npm install -g @danubedata/cli

      - run: danube pages deploy --dir ./dist
        env:
          DANUBE_TOKEN: ${{ secrets.DANUBE_TOKEN }}
          DANUBE_SITE_ID: ${{ secrets.DANUBE_SITE_ID }}
          DANUBE_TEAM_ID: ${{ secrets.DANUBE_TEAM_ID }}

Update notifications

The CLI checks for updates automatically (once per 24 hours). Notifications are suppressed in CI environments or when DANUBE_NO_UPDATE_CHECK is set.

Exit codes

Next steps

• CLI: VPS Instances — Manage VPS instances
• CLI: Object Storage — Manage buckets and access keys
• CLI: Static Sites — Deploy and manage static sites
• CLI: Serverless Containers — Deploy and manage containers
• API Authentication — Create API tokens

Questions? Contact support at support@danubedata.ro