v3.0

#5 Thanks to @igoragatti, instead of only having the exclude option, you can pass more optional params with the extra param of this action.

For more Information, please read the readme

v2.2

Added exclude option in order to exclude paths from rsync

Full Changelog: v2.1...v2.2

v2.1

Removed -l option until I found out how to use the --safe-links option

v2

In order to keep this project as clean as possible. I will remove at some point all other versions but this one (and a new v1 without the delete option).
Please use version 2 for full functionality.

v1.5

Thanks to age992 and vintertown the bug with the delete option was fixed and the -l option for symlinks was added.

I am planning on writing a wiki with all functionalities explained.

v1.4

It was requested, that I add the delete option to the rsync deployment. see #1

That way, files that are not present at the source anymore, will also be deleted on the destination.
Please be advised to check your paths accordingly. Because due to this change, it might happen that you delete directories that you are not intending on deleting.

Therefore I added better output on the console. It should be listed there, how many files were deleted.

v1.3

Bugfix for the if condition

v1.2

Fixed run after commands and made coder faster

v1.1

Added just a few cosmetic changes to the readme and marketplace view.

v1

action-sshpass-rsync

Github Action to deploy via rsync and sshpass
in order to enable deployments on hosts, which don't support key based ssh

Usage

- name: Deploy to Server
  uses: inf166/action-sshpass-rsync@v1
  with:
    host: ${{ secrets.DEPLOY_HOST }}
    user: ${{ secrets.DEPLOY_USER }}
    port: ${{ secrets.DEPLOY_PORT }}
    pass: ${{ secrets.DEPLOY_PASS }}
    local: "path/of/your/local/mashine"
    remote: "path/where/to/deploy/to"
    runBeforeDeployment: |
      cd somewhere/
    runAfterDeployment: |
      cd ../somewhere/back/to

You can do something before and after your deployment on the remote.
For this, you use the runBeforeDeployment and runAfterDeployment inputs.

Optional (and not firmly tested)

You can use your private key and just enjoy the deployment part of this action.
But I must say, that I have not tested this.
Feel free to contribute.

- name: Deploy to Server
  uses: inf166/action-sshpass-rsync@v1
  with:
    host: ${{ secrets.DEPLOY_HOST }}
    user: ${{ secrets.DEPLOY_USER }}
    port: ${{ secrets.DEPLOY_PORT }}
    key: ${{ secrets.PRIVATE_KEY }}
    local: "path/of/your/local/mashine"
    remote: "path/where/to/deploy/to"
    runBeforeDeployment: |
      cd somewhere/
    runAfterDeployment: |
      cd ../somewhere/back/to

Disclaimer

Parts of this action are heavily inspired by
matheusvanzan / sshpass-action
and
D3rHase / rsync-deploy-action.

I have looked up how to make my own action there and build upon their code.
So please give them some love.