Skip to content

Commit e525a87

Browse files
committed
Include ssh -o CertificateFile in README usage example
Technically not needed as long as the certificate filename is constructed with a `-cert.pub` suffix, which it is in this Action. Yet being explicit about the certificate filename has the indirect benefit of _ssh_ going directly for the certificate, rather than first attempting and failing on using the regular public key.
1 parent cca37fa commit e525a87

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,11 @@ jobs:
3131
- name: Deploy site
3232
if: github.ref == 'refs/heads/main'
3333
run: >
34-
rsync -e "ssh -i '$SSH_KEY_PATH'"
34+
rsync -e "ssh -o IdentityFile='$SSH_KEY_PATH' -o CertificateFile='$SSH_CERT_PATH'"
3535
--verbose --recursive --delete-after --perms --chmod=D755,F644
3636
build/ deployer@site.example.net:/var/www/site/
3737
env:
38+
SSH_CERT_PATH: ${{ steps.ssh_cert.outputs.cert_path }}
3839
SSH_KEY_PATH: ${{ steps.ssh_cert.outputs.key_path }}
3940
```
4041

0 commit comments

Comments
 (0)