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 sentence

Browse source
This commit is contained in:
shimataro 2020-01-26 18:05:01 +09:00
parent c7a23d2dfd
commit b6835ff49c
No known key found for this signature in database
GPG key ID: BE92C05736911A9D
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -103,8 +103,8 @@ Here are some methods:
I recommend **rsync via bastion**. I recommend **rsync via bastion**.
It has some advantages over other methods: It has some advantages over other methods:
* You only need to use this action **only once** even if it is necessary to transfer to multiple servers. * This action is required **only once** even if it is necessary to transfer files to multiple servers.
* Other methods require to use it multiple times in order to connect to each servers. * Other methods require to use this action multiple times in order to connect to each servers.
* 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. * 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.