smbcloud-deploy-rsync

To ensure rsync parity, source paths with a trailing slash copy directory contents, while destination paths with a slash copy into the directory. The Rust CLI deployment path normalizes these remote paths to match shell rsync semantics exactly.

SSH identity handling for remote deploy targets involves resolving and applying the correct SSH keys within the Rust CLI. The deployment path ensures proper host:path syntax is used while the embedded Rust rsync client manages the secure connection.

Workspace wiring for rsync deployments involves integrating the rsync_deploy.rs module into your Rust CLI. This setup ensures workspace dependencies are correctly configured to execute the generic deployment path without errors.

Debugging rsync path normalization requires verifying host:path syntax and trailing slash rules within your Rust CLI. Running a dry-run deployment against a test project helps isolate and resolve parity mismatches with shell rsync commands.

Yes, an embedded Rust rsync client executes generic deployments directly. It applies remote path normalization and SSH identity handling internally, ensuring parity with shell rsync without needing external system shell commands.

This happens when source path trailing slash semantics are mismatched. In rsync, a source path without a trailing slash copies the directory itself, while adding a slash copies only the contents into the normalized remote destination path.