2019-02-09 21:19:13 +08:00
# rsync deployments
2019-02-09 21:17:45 +08:00
2019-12-04 23:08:15 +08:00
Forked from [Contention/rsync-deployments ](https://github.com/Contention/rsync-deployments )
2019-11-13 07:45:15 +08:00
This GitHub Action deploys files in `GITHUB_WORKSPACE` to a folder on a server via rsync over ssh.
2019-02-09 21:17:45 +08:00
2019-11-13 07:45:15 +08:00
Use this action in a build/test workflow which leaves deployable code in `GITHUB_WORKSPACE` .
2019-02-09 21:17:45 +08:00
2019-12-05 02:09:24 +08:00
---
2019-12-05 02:11:03 +08:00
## Inputs
2019-02-09 21:17:45 +08:00
2019-12-05 01:41:36 +08:00
- `switches` * - The first is for any initial/required rsync flags, eg: `-avzr --delete`
2019-02-09 21:17:45 +08:00
2019-12-05 02:02:32 +08:00
- `rsh` - Remote shell commands
2019-11-13 06:39:54 +08:00
2019-12-05 01:35:52 +08:00
- `path` - The source path. Defaults to GITHUB_WORKSPACE
2019-02-09 21:17:45 +08:00
2019-12-05 01:35:52 +08:00
- `remote_path` * - The deployment target path
2019-02-09 21:17:45 +08:00
2019-12-05 01:28:33 +08:00
- `remote_host` * - The remote host
2019-02-09 21:17:45 +08:00
2019-12-05 01:58:49 +08:00
- `remote_port` - The remote port. Defaults to 22
2019-12-05 01:28:33 +08:00
- `remote_user` * - The remote user
2019-11-13 06:39:54 +08:00
2019-12-05 01:28:33 +08:00
- `remote_key` * - The remote ssh key
2019-12-05 01:37:11 +08:00
``* = Required``
2019-12-05 01:28:33 +08:00
2019-12-05 02:09:24 +08:00
## Required secret
2019-12-05 01:28:33 +08:00
This action needs a `DEPLOY_KEY` secret variable. This should be the private key part of a ssh key pair. The public key part should be added to the authorized_keys file on the server that receives the deployment. This should be set in the Github secrets section and then referenced as the `remote_key` input.
2019-02-09 21:17:45 +08:00
2019-12-05 02:09:24 +08:00
## Example usage
2019-02-09 21:17:45 +08:00
2019-12-05 01:28:33 +08:00
Simple:
2019-02-09 21:17:45 +08:00
```
2019-09-15 02:33:49 +08:00
name: DEPLOY
on:
push:
branches:
- master
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: rsync deployments
2019-12-05 01:39:07 +08:00
uses: burnett01/rsync-deployments@2.0
2019-09-15 02:33:49 +08:00
with:
2019-12-05 01:28:33 +08:00
switches: -avzr --delete
2019-09-15 02:33:49 +08:00
path: src/
2019-12-05 01:28:33 +08:00
remote_path: /var/www/html/
remote_host: example.com
remote_user: debian
remote_key: ${{ secrets.DEPLOY_KEY }}
```
2019-09-15 02:33:49 +08:00
2019-12-05 01:28:33 +08:00
Advanced:
2019-09-15 02:33:49 +08:00
2019-02-09 21:17:45 +08:00
```
2019-12-05 01:28:33 +08:00
name: DEPLOY
on:
push:
branches:
- master
2019-02-09 21:17:45 +08:00
2019-12-05 01:28:33 +08:00
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: rsync deployments
2019-12-05 01:39:07 +08:00
uses: burnett01/rsync-deployments@2.0
2019-12-05 01:28:33 +08:00
with:
switches: -avzr --delete --exclude="" --include="" --filter=""
path: src/
remote_path: /var/www/html/
remote_host: example.com
2019-12-05 02:06:58 +08:00
remote_port: 5555
2019-12-05 01:28:33 +08:00
remote_user: debian
remote_key: ${{ secrets.DEPLOY_KEY }}
```
2019-02-09 21:17:45 +08:00
2019-12-05 02:02:32 +08:00
For better security, I suggest you create additional secrets for remote_host, remote_port and remote_user inputs.
2019-12-05 01:35:52 +08:00
```
name: DEPLOY
on:
push:
branches:
- master
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: rsync deployments
2019-12-05 01:39:07 +08:00
uses: burnett01/rsync-deployments@2.0
2019-12-05 01:35:52 +08:00
with:
switches: -avzr --delete
path: src/
remote_path: /var/www/html/
remote_host: ${{ secrets.DEPLOY_HOST }}
2019-12-05 02:02:32 +08:00
remote_port: ${{ secrets.DEPLOY_PORT }}
2019-12-05 01:35:52 +08:00
remote_user: ${{ secrets.DEPLOY_USER }}
remote_key: ${{ secrets.DEPLOY_KEY }}
```
2019-12-05 02:09:24 +08:00
---
## Version 1.0 (EOL)
Looking for version 1.0?
Check here: https://github.com/Burnett01/rsync-deployments/tree/1.0
Please note that version 1.0 has reached end of life state.