Remote Nodes
Multi-Environment
By setting up remote nodes, you can access separate Dagu deployments, such as development, staging, and production, from one Dagu Web UI. Each remote deployment keeps its own scheduler, workers, storage, credentials, and runtime configuration.
See Multi-Environment Deployments for the recommended isolation and Git Sync promotion model.
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}"To read a password or token from a file, such as a mounted Docker or Kubernetes secret, set basic_auth_password_file or auth_token_file instead of the value. See Secrets From Files.
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. See Remote Nodes Authentication for detailed setup instructions.