SSH & SFTP

baudelaire deploy also targets any host reachable over SSH, transferring files with SFTP. Add an ssh block instead of (or alongside) an s3 one:

deploy {
  ssh {
    host "example.com"
    path "/var/www/site"
    key "~/.ssh/id_ed25519"
  }
}

host

server hostname or IP. Required.

path

absolute remote directory the build is mirrored into. Required.

port (22)

SSH port.

user

user to authenticate as. Defaults to $USER.

key

path to a private key (absolute, ~-relative, or under the project root). Unset tries the ssh-agent, then a password.

strict (#true)

verify the server’s host key against ~/.ssh/known_hosts: learning an unseen host on first connect and refusing a changed key. Set #false to accept any key (StrictHostKeyChecking=no).

delete (#true)

remove remote files under path that the build no longer produces.

Authentication

Baudelaire tries, in order: the configured key (supply its passphrase, if any, like any other secret below); the ssh-agent at $SSH_AUTH_SOCK, offering each identity it holds; then a password from BAUDELAIRE_SSH_PASSWORD, stdin (--secret -), or the prompt. A configured key is used exclusively: the agent and password are only tried when no key is set.

Change detection

Baudelaire runs sha256sum on the host and diffs it against the local files, so an unchanged file is never re-sent. If the host cannot run it (a bare directory, a non-coreutils system), every file simply uploads; the deploy is still correct, just not incremental that run.