actions/ssh-key-action
1
0
Fork 0
mirror of https://github.com/shimataro/ssh-key-action.git synced 2025-06-19 22:52:10 +10:00
Code Activity

* update sentences

Browse source
This commit is contained in:
shimataro 2020-01-26 22:10:49 +09:00
parent 6c1366e61a
commit 36dcca4a76
No known key found for this signature in database
GPG key ID: BE92C05736911A9D
1 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -103,10 +103,9 @@ Here are some solutions:
I recommend **rsync via bastion**. I recommend **rsync via bastion**.
It has some advantages over other methods: It has some advantages over other methods:
* This action is required **only once** even if it is necessary to transfer files to multiple servers. * "Rsync via bastion" doesn't require to update workflow files and `secrets` even if it is necessary to transfer files to multiple servers.
* Other methods require to use this action multiple times in order to connect to each servers. * Other methods require to update `known-hosts` if servers have changed.
* Of course, it is necessary to install bastion public key on servers, and server keys on bastion. But you don't have to update workflow files and `secrets` even if number of servers changed. * Rsync:
* `rsync`:
* is faster than others. * is faster than others.
* does **NOT** break files even if disconnected during transferring. * does **NOT** break files even if disconnected during transferring.
* can remove files that don't exist in server. * can remove files that don't exist in server.