Go to file
github-actions 5d811fd34f chore(release): 3.1.0 [skip ci]
# [3.1.0](https://github.com/easingthemes/ssh-deploy/compare/v3.0.1...v3.1.0) (2022-12-31)

### Features

* add e2e tests ([40f855a](40f855a08b))
2022-12-31 09:34:03 +00:00
.github/workflows readd workflows 2022-12-31 10:25:56 +01:00
dist Remove Key log 2022-12-31 10:30:19 +01:00
docs chore(release): 3.1.0 [skip ci] 2022-12-31 09:34:03 +00:00
src Remove Key log 2022-12-31 10:30:19 +01:00
test permissions fix 2022-12-31 10:20:28 +01:00
.editorconfig [tests] add editorconfig and eslint 2020-04-11 16:26:19 +02:00
.eslintrc.js [tests] add editorconfig and eslint 2020-04-11 16:26:19 +02:00
.gitignore start e2e 2022-12-29 15:46:56 +01:00
.releaserc fix: add assets to semantic-release git 2021-05-28 01:23:17 +02:00
LICENSE [init]: update Licence 2019-09-25 23:54:12 +02:00
README.md feat: add e2e tests 2022-12-31 10:33:16 +01:00
action.yml BREAKING CHANGE: update to use nodeJS v16 2022-10-28 03:44:28 +02:00
package-lock.json revert wrong package 2022-12-31 10:24:28 +01:00
package.json chore(release): 3.1.0 [skip ci] 2022-12-31 09:34:03 +00:00

README.md

ssh deployments

Deploy code with rsync over ssh, using NodeJS.

NodeJS version is more than a minute faster than simple Docker version.

This GitHub Action deploys specific directory from GITHUB_WORKSPACE to a folder on a server via rsync over ssh, using NodeJS.

This action would usually follow a build/test action which leaves deployable code in GITHUB_WORKSPACE, eg dist;

Configuration

Pass configuration with env vars

1. SSH_PRIVATE_KEY [required]

Private key part of an SSH key pair. The public key part should be added to the authorized_keys file on the server that receives the deployment.

More info for SSH keys: https://www.ssh.com/ssh/public-key-authentication

The keys should be generated using the PEM format. You can use this command

ssh-keygen -m PEM -t rsa -b 4096
2. REMOTE_HOST [required]

eg: mydomain.com

3. REMOTE_USER [required]

eg: myusername

4. REMOTE_PORT (optional, default '22')

eg: '59184'

5. ARGS (optional, default '-rltgoDzvO')

For any initial/required rsync flags, eg: -avzr --delete

6. SOURCE (optional, default '')

The source directory, path relative to $GITHUB_WORKSPACE root, eg: dist/

7. TARGET (optional, default '/home/REMOTE_USER/')

The target directory

8. EXCLUDE (optional, default '')

path to exclude separated by ,, ie: /dist/, /node_modules/

Usage

Use the latest version from Marketplace,eg: ssh-deploy@v2 or use the latest version from a branch, eg: ssh-deploy@main

  - name: Deploy to Staging server
    uses: easingthemes/ssh-deploy@main
    env:
      SSH_PRIVATE_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
      ARGS: "-rltgoDzvO"
      SOURCE: "dist/"
      REMOTE_HOST: ${{ secrets.REMOTE_HOST }}
      REMOTE_USER: ${{ secrets.REMOTE_USER }}
      TARGET: ${{ secrets.REMOTE_TARGET }}
      EXCLUDE: "/dist/, /node_modules/"

Example usage in workflow

name: Node CI

on: [push]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v1
    - name: Install Node.js
      uses: actions/setup-node@v1
      with:
        node-version: '10.x'
    - name: Install npm dependencies
      run: npm install
    - name: Run build task
      run: npm run build --if-present
    - name: Deploy to Server
      uses: easingthemes/ssh-deploy@main
      env:
          SSH_PRIVATE_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
          ARGS: "-rltgoDzvO --delete"
          SOURCE: "dist/"
          REMOTE_HOST: ${{ secrets.REMOTE_HOST }}
          REMOTE_USER: ${{ secrets.REMOTE_USER }}
          TARGET: ${{ secrets.REMOTE_TARGET }}
          EXCLUDE: "/dist/, /node_modules/"

Issues

Almost 95% of the issues are related to wrong SSH connection. I've added e2e test for this action. Check actions tab for example.

Check manually your ssh connection from your client before opening a bug report. Thanks.

Disclaimer

Check your keys. Check your deployment paths. And use at your own risk.