sultann/Remote Deploy Action
Deploy files to remote servers via SSH and rsync with build support and flexible exclusions
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| remote-host | Remote server hostname or IP address | yes | — |
| remote-user | Remote SSH username | yes | — |
| remote-key | SSH private key content | yes | — |
| remote-port | Remote SSH port | no | 22 |
| source-path | Local source directory relative to workspace (e.g., ./ or dist/) | no | ./ |
| target-path | Remote target directory (absolute path) | yes | — |
| ignore-file | Path to ignore file (.distignore, .deployignore, etc.) | no | .distignore |
| script-before | Script to run locally before deployment (npm build, composer install, etc.) | no | "" |
| script-after | Script to run on remote server after deployment (cache flush, migrations, etc.) | no | "" |
| dry-run | Preview deployment without actually deploying | no | false |
| rsync-options | Custom rsync options | no | -avz --delete |
| slack-webhook | Slack webhook URL for notifications | no | "" |
| slack-notify | When to send Slack notification: success, failure, or always | no | success |
| project-url | Project URL for notifications (e.g., https://example.com or repo name) | no | "" |
Outputs
no outputs