malwador/Deploy WordPress to Kinsta via sFTP
Efficiently deploy WordPress files to Kinsta hosting via sFTP with selective file synchronization
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Aug 8, 2025
- License
- None
Pinned Snippet
uses: malwador/kinsta-deployment@de43173a34cbda8819b76e11ffc8ed214a3560db # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| kinsta_host_ip | Kinsta sFTP host IP address (required due to Cloudflare) | yes | — |
| kinsta_username | Kinsta sFTP username | yes | — |
| kinsta_password | Kinsta sFTP password | yes | — |
| kinsta_port | Kinsta sFTP port (each site has a unique port) | yes | — |
| source_path | Local source path to deploy (relative to repository root) | no | . |
| target_path | Remote target path on Kinsta server | yes | — |
| exclude_patterns | Comma-separated list of patterns to exclude from deployment | no | .git,.github,node_modules,.env,.DS_Store,*.log |
| dry_run | Perform a dry run without actually transferring files | no | false |
| verbose | Enable verbose logging | no | false |
| skip_wp_cli | Skip wp-cli post-deployment actions | no | false |
| install_kinsta_mu_plugin | Download and install Kinsta MU Plugin | no | true |
| kinsta_mu_plugin_path | Custom path for Kinsta MU Plugin installation (relative to target_path) | no | wp-content/mu-plugins |
| purge_kinsta_cache | Purge Kinsta cache after deployment using WP-CLI | no | true |
Outputs
| name | description |
|---|---|
| files_transferred | Number of files transferred |
| bytes_transferred | Total bytes transferred |
| deployment_time | Time taken for deployment in seconds |