ssh-dev-suite/deploy

You can deploy local projects to a remote server using incremental sync by running a configured deploy script that transfers only changed files via rsync over SSH, reducing bandwidth and deployment time.

Yes, you can execute pre and post deployment hooks during a remote SSH deploy by defining them in your config.yaml file, allowing you to run custom scripts before or after the incremental sync completes.

The best way to rollback a remote server deployment is using the dedicated rollback command in the deployment script, which reverts the remote server to its previous stable version profile.

Yes, you need rsync and python3 installed locally to use config-driven SSH deployment profiles, as the tool relies on these dependencies for incremental file synchronization and configuration parsing.

Incremental sync handles deployment to remote servers by detecting local file modifications and transferring only the updated files over SSH, ensuring faster deployments compared to full directory syncs.

Yes, you can manage multiple remote server deployments using configuration profiles defined in config.yaml, allowing you to specify distinct remote servers, hooks, and sync rules for each project.