Remote Nodes

Multi-Environment

By setting up remote nodes, you can run workflows on different Dagu server environments (e.g., development, staging, production) in a single Dagu server Web UI.

remote_nodes:
  - name: "development"
    api_base_url: "http://dev.internal:8080/api/v1"
    auth_type: basic
    basic_auth_username: "dev"
    basic_auth_password: "${DEV_PASSWORD}"

  - name: "staging"
    api_base_url: "https://staging.example.com/api/v1"
    auth_type: token
    auth_token: "${STAGING_TOKEN}"

  - name: "production"
    api_base_url: "https://prod.example.com/api/v1"
    auth_type: token
    auth_token: "${PROD_TOKEN}"

Using API Keys for Remote Access

When remote nodes use Builtin Authentication, you can use API Keys for secure, role-based access:

remote_nodes:
  - name: "production"
    api_base_url: "https://prod.example.com/api/v1"
    auth_type: token
    auth_token: "dagu_7Kq9mXxN3pLwR5tY2vZa8bCdEfGhJk4n6sUwXy0zA1B"

API keys provide fine-grained role-based permissions (admin, manager, developer, operator, viewer) and usage tracking. Community self-hosted servers can create up to 2 API keys without an active self-host license; larger remote-node setups that need more service keys should use an active license on the server where the keys are created. See Remote Nodes Authentication for detailed setup instructions.

See Also

• Server Configuration
• Remote Nodes Authentication
• API Keys