rsync-deployments/README.md

169 lines
4.3 KiB
Markdown
Raw Normal View History

2019-02-09 14:19:13 +01:00
# rsync deployments
2019-02-09 14:17:45 +01:00
2019-12-27 16:29:01 +01:00
This GitHub Action deploys files in `GITHUB_WORKSPACE` to a remote folder via rsync over ssh.
2019-02-09 14:17:45 +01:00
2019-12-27 16:29:01 +01:00
Use this action in a CD workflow which leaves deployable code in `GITHUB_WORKSPACE`.
2020-01-05 14:47:18 +01:00
The underlaying base-image of the docker-image is very small (Alpine (no cache)) which results in fast deployments.
2019-02-09 14:17:45 +01:00
2019-12-04 19:09:24 +01:00
---
2019-12-04 19:11:03 +01:00
## Inputs
2019-02-09 14:17:45 +01:00
2019-12-04 18:41:36 +01:00
- `switches`* - The first is for any initial/required rsync flags, eg: `-avzr --delete`
2019-02-09 14:17:45 +01:00
2019-12-04 19:02:32 +01:00
- `rsh` - Remote shell commands
2019-11-12 23:39:54 +01:00
2019-12-04 18:35:52 +01:00
- `path` - The source path. Defaults to GITHUB_WORKSPACE
2019-02-09 14:17:45 +01:00
2019-12-04 18:35:52 +01:00
- `remote_path`* - The deployment target path
2019-02-09 14:17:45 +01:00
- `remote_host`* - The remote host
2019-02-09 14:17:45 +01:00
2019-12-04 18:58:49 +01:00
- `remote_port` - The remote port. Defaults to 22
- `remote_user`* - The remote user
2019-11-12 23:39:54 +01:00
- `remote_key`* - The remote ssh key
2019-12-04 18:37:11 +01:00
``* = Required``
2019-12-04 19:09:24 +01:00
## Required secret
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 14:17:45 +01:00
2019-12-04 19:09:24 +01:00
## Example usage
2019-02-09 14:17:45 +01:00
Simple:
2019-02-09 14:17:45 +01:00
```
name: DEPLOY
on:
push:
branches:
- master
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: rsync deployments
2020-06-23 00:08:44 +02:00
uses: burnett01/rsync-deployments@4.1
with:
switches: -avzr --delete
path: src/
remote_path: /var/www/html/
remote_host: example.com
remote_user: debian
remote_key: ${{ secrets.DEPLOY_KEY }}
```
Advanced:
2019-02-09 14:17:45 +01:00
```
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: rsync deployments
2020-06-23 00:08:44 +02:00
uses: burnett01/rsync-deployments@4.1
with:
switches: -avzr --delete --exclude="" --include="" --filter=""
path: src/
remote_path: /var/www/html/
remote_host: example.com
2019-12-04 19:06:58 +01:00
remote_port: 5555
remote_user: debian
remote_key: ${{ secrets.DEPLOY_KEY }}
```
2019-02-09 14:17:45 +01:00
2019-12-04 19:02:32 +01:00
For better security, I suggest you create additional secrets for remote_host, remote_port and remote_user inputs.
2019-12-04 18:35:52 +01:00
```
2019-12-27 16:37:44 +01:00
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
2019-12-04 18:35:52 +01:00
- name: rsync deployments
2020-06-23 00:08:44 +02:00
uses: burnett01/rsync-deployments@4.1
2019-12-04 18:35:52 +01:00
with:
switches: -avzr --delete
path: src/
remote_path: /var/www/html/
remote_host: ${{ secrets.DEPLOY_HOST }}
2019-12-04 19:02:32 +01:00
remote_port: ${{ secrets.DEPLOY_PORT }}
2019-12-04 18:35:52 +01:00
remote_user: ${{ secrets.DEPLOY_USER }}
remote_key: ${{ secrets.DEPLOY_KEY }}
```
2019-12-04 19:09:24 +01:00
---
2020-01-05 14:47:18 +01:00
## Version 3.0
Looking for version 3.0?
Check here: https://github.com/Burnett01/rsync-deployments/tree/3.0
Version 3.0 uses the ``alpine:latest`` base-image directly.<br>
Consider upgrading to 4.0 that uses a docker-image ``drinternet/rsync:1.0.1`` that is<br>
based on ``alpine:latest``and heavily optimized for rsync.
2019-12-27 16:33:45 +01:00
## Version 2.0
Looking for version 2.0?
Check here: https://github.com/Burnett01/rsync-deployments/tree/2.0
Version 2.0 uses a larger base-image (``ubuntu:latest``).<br>
Consider upgrading to 3.0 for even faster deployments.
2019-12-04 19:09:24 +01: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.
2020-01-08 20:10:18 +01:00
---
## Acknowledgements
+ This project is a fork of [Contention/rsync-deployments](https://github.com/Contention/rsync-deployments)
+ Base image [JoshPiper/rsync-docker](https://github.com/JoshPiper/rsync-docker)
2020-10-05 18:46:16 +02:00
---
## Media
This action was featured in multiple blogs across the globe:
- https://leobrack.co.uk/blog/2020-02-15-automatically-push-changes-to-your-live-site-with-github-actions
- https://blog.maniak.co/ci-cd-for-wordpress/
- https://elijahverdoorn.com/2020/04/14/automating-deployment-with-github-actions/
- https://www.vektor-inc.co.jp/post/github-actions-deploy/
- https://ews.ink/tech/blog-deploy-2/
- https://webpick.info/automatiser-avec-github-actions/
2020-01-08 20:10:18 +01:00
2021-04-03 15:02:42 +02:00
- https://matthias-andrasch.eu/blog/2021/tutorial-webseite-mittels-github-actions-deployment-zu-uberspace-uebertragen-rsync/
- https://mikael.koutero.me/posts/hugo-github-actions-deploy-rsync/
- https://cdmana.com/2021/02/20210208122400688I.html
- https://jishuin.proginn.com/p/763bfbd38928
- https://cloud.tencent.com/developer/article/1786522
- http://www.ningco.cn/github_action_deploy_blog/
- https://qdmana.com/2021/01/20210127094413405u.html