Keypair created (private key stays local and hidden; the public key is safe to share). Here's the public key you'll authorize in the BWU cPanel:

Now let me add the SSH alias locally. The BWU cPanel username is almost certainly fortunepublish (that's the database prefix, which mirrors the cPanel account name) — I'll set the alias to that and we'll confirm on the test.

Done on my end — keypair generated (fortunepublish_deploy) and alias bwu-production added to your SSH config. Now the one step only you can do: authorize the public key inside the BWU account's cPanel.

Your steps (in the BWU cPanel)

1. Log into the BWU account's cPanel (the fortunepublish account) — e.g. https://209.74.93.82:2083, or via WHM → List Accounts → fortunepublish → Log in to cPanel.
2. Go to Security → SSH Access → Manage SSH Keys.
3. Click Import Key, then:
   • Public Key box → paste this exact line:

     ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJDlVvAr90lBh0q0yfuIZ2dKSv47MGSAQ3ZYk+NY5QeI fortunepublish_deploy
   • Leave the Private Key box empty. Name it fortunepublish_deploy. Click Import.
4. Back on Manage SSH Keys, find the key under Public Keys → Manage → Authorize (status should flip to authorized).
5. Make sure Shell Access is enabled for the account (if not: WHM → Modify Account → Privileges → check Shell Access → Save — same path as before).

Two things to confirm back to me

• The cPanel username shown top-right in that cPanel — I set the alias to fortunepublish. If it's different, tell me and I'll fix the alias.
• Just say "authorized" when done.

Then I'll run a read-only test (ssh bwu-production "whoami; pwd"), locate the bookwritinguniversity.com docroot, back up the file(s), and build the /all-access page — after which I'll finish the $29/mo subscription + payment link and complete the Groupon draft.

One note: your private key never leaves the machine and I won't display it — only the public key above (which is safe to share) gets authorized.