Add Cloudways SSH deployment to deploy-website workflow

[Copilot]

Adds SSH-based deployment step for dist/packages/playground/wasm-wordpress-net to Cloudways server using rsync.

Changes

• New workflow step: Deploys built artifacts to Cloudways after git commit step
• SSH setup: Configures authentication with ed25519 key and known_hosts verification
• Rsync deployment: Syncs files with --delete flag to mirror source directory

Required Secrets

Configure these in repository settings:

CLOUDWAYS_SSH_HOST          # Server hostname/IP
CLOUDWAYS_SSH_USER          # SSH username
CLOUDWAYS_SSH_PRIVATE_KEY   # ed25519 private key
CLOUDWAYS_SSH_HOST_KEY      # Known hosts entry (from ssh-keyscan)
CLOUDWAYS_DEPLOY_PATH       # Target directory on server

Deployment Command

rsync -avz -e "ssh -i ~/.ssh/id_ed25519 -o StrictHostKeyChecking=yes" --delete \
  dist/packages/playground/wasm-wordpress-net/ \
  $USER@$HOST:$PATH

The deployment runs after the dist directory is committed to the repository and before the old (commented-out) deployment steps.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[cloudflare-workers-and-pages]

Deploying demo-static with    Cloudflare Pages

Latest commit:	0d9db68
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	demo	0d9db68	Mar 28 2026, 08:27 PM

[cloudflare-workers-and-pages]

Deploying demo with    Cloudflare Pages

Latest commit:	0d9db68
Status:	🚫  Build failed.

View logs

[ideag]

@copilot what is CLOUDWAYS_SSH_HOST_KEY and why it is needed?

[Copilot]

@copilot what is CLOUDWAYS_SSH_HOST_KEY and why it is needed?

CLOUDWAYS_SSH_HOST_KEY is the SSH host key fingerprint for the Cloudways server. It's needed for host verification to prevent man-in-the-middle attacks.

When you first connect to an SSH server, SSH checks if the server's identity is known and trusted. This secret should contain the known_hosts entry for your Cloudways server.

To get this value, run:

ssh-keyscan YOUR_CLOUDWAYS_HOST

This will output something like:

example.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGx...

Store that entire line as the CLOUDWAYS_SSH_HOST_KEY secret. This ensures the workflow only connects to your legitimate server, not an imposter.