SSH

Emcee client may use SSH to deploy queue server and workers to the machines. You have to explicitly set type to deploy in emceeplan to tell Emcee to deploy itself :

```yml queue: type: deploy #...

Next, specify deployment configuration for `queue` and `workers` in emceeplan defining `host`, `ssh` and optional `id` for workers:

 ```yml
queue:
  type: deploy
  host: localhost
  ssh:
    username: _emcee
    identity:
      type: publicKey
      keyPath: /Users/YOUR_USER/.ssh/id_ed25519_emcee
  workers:
    - host: localhost
      #...

host

FQDN, ip or hostname where queue or worker should be deployed. For instance, worker777.com, 10.8.0.1, localhost.

ssh

For SSH access you configure username and identity. The latter in turn may be of type publicKey or password.

You should configure ssh identity for queue and this identity will be used for workers by default. You may override ssh configuration for every worker if needed this way:

```yml queue: type: deploy #... ssh: username: some_user_0 identity: #... workers: - ssh: username: some_user_1 identity: #... #... - ssh: username: some_user_2 identity: #... #...

### public key authentication

```yml
  ssh:
    username: _emcee
    identity:
      type: publicKey
      keyPath: /Users/YOUR_USER/.ssh/id_ed25519_emcee
  #...

Modern MacOS does not support rsa keys. id_ed25519 or dsa are recommended instead

If you encounter problems with ssh deployment check private key file permissions

password authentication

  ssh:
    username: _emcee
    identity:
      type: password
      password: YOUR_PASSWORD
  #...

worker id

Setting worker id actually affects only analytics and logs, so use it to increase system observability.

If omit hostname will be used as worker id.