daoflow server add

Register a Docker target and run readiness verification immediately.

Usage

daoflow server add [options]

Required Scope

• server:write

Options

Flag	Description
--name <name>	Stable server name
--host <host>	Hostname or IP address
--region <region>	Region label, defaults to default
--ssh-port <port>	SSH port, defaults to 22
--ssh-user <user>	SSH user, defaults to root
--ssh-key <path>	Path to an SSH private key file
--ssh-private-key <pem>	Inline SSH private key material
--ssh-key-id <id>	Reuse a managed SSH key asset
--kind <kind>	docker-engine or docker-swarm-manager
--dry-run	Preview the payload and exit with code 3
--yes	Confirm the registration
--json	Emit the standard JSON envelope

Examples

daoflow server add \
  --name edge-vps-1 \
  --host 203.0.113.42 \
  --region us-west-2 \
  --ssh-user deploy \
  --ssh-key ~/.ssh/daoflow_ed25519 \
  --yes

daoflow server add \
  --name local-dev \
  --host localhost \
  --region local \
  --yes \
  --json

JSON Success Shape

{
  "ok": true,
  "data": {
    "server": {
      "id": "srv_edge_vps_1",
      "name": "edge-vps-1",
      "host": "203.0.113.42",
      "region": "us-west-2",
      "sshPort": 22,
      "sshUser": "deploy",
      "kind": "docker-engine",
      "status": "ready",
      "dockerVersion": "27.5.1",
      "composeVersion": "2.34.0"
    },
    "readiness": {
      "readinessStatus": "ready",
      "sshReachable": true,
      "dockerReachable": true,
      "composeReachable": true,
      "latencyMs": 42,
      "checkedAt": "2026-03-20T22:05:00.000Z",
      "issues": [],
      "recommendedActions": ["No action required."]
    }
  }
}

Notes

• Registration immediately runs the same readiness verification flow used by the dashboard.
• Raw SSH private keys are stored as managed SSH key assets and linked back to the server. Use --ssh-key-id to reuse an existing managed key instead of uploading private material again.
• If SSH works but Docker or Compose does not, the command returns structured issues and recommended actions instead of a silent partial success.
• Read-only principals still use daoflow status and daoflow doctor for inspection without mutation.
• docker-swarm-manager targets participate in Swarm stack deploy and rollback flows once a compose-backed service points at them.
• Swarm execution currently requires published-port readiness probes; internal-network probes still fail planning and execution.

Server Operations

daoflow server ops resources --server srv_123 --json
daoflow server ops cleanup --server srv_123 --dry-run --json
daoflow server ops cleanup --server srv_123 --yes
daoflow server ops patch --server srv_123 --json
daoflow server ops swarm refresh-topology --server srv_123 --json
daoflow server ops swarm node availability --server srv_123 --node worker-a --availability drain --dry-run --json
daoflow server ops swarm service scale --server srv_123 --service stack_api --replicas 3 --dry-run --json
daoflow server ops history --server srv_123 --json
daoflow server ops logs --operation op_123 --json

Resource, history, and operation-log reads use server:read. Cleanup and patch commands use server:write; live cleanup requires --yes. Swarm topology refresh, node availability changes, and service scaling also use server:write; node and scale dry-runs create durable plan operations, while live changes require --yes.

Access Assets

Reusable SSH keys and custom certificates are managed through daoflow access-assets.

daoflow access-assets ssh-key list --json
daoflow access-assets ssh-key create --name prod-deploy --private-key-file ~/.ssh/daoflow_ed25519 --yes
daoflow access-assets ssh-key rotate --key-id key_123 --private-key-file ~/.ssh/daoflow_ed25519.new --yes
daoflow access-assets ssh-key attach --key-id key_123 --server-id srv_123 --yes
daoflow access-assets ssh-key detach --server-id srv_123 --yes
daoflow access-assets certificate list --json
daoflow access-assets certificate create --name wildcard-example --cert-file ./fullchain.pem --private-key-file ./privkey.pem --yes

List commands require server:read. Create, rotate, attach, and delete commands require server:write and never print private key, certificate, or encrypted secret material.