Skip to content

Commit ccdec6d

Browse files
committed
update variable names in readme
1 parent da9bb84 commit ccdec6d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,6 @@ action "Git Push to Production" {
4747
## Setting up your SSH keys
4848

4949
1. [Generate a new SSH key pair](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/) as a special deploy key. The simplest method is to generate a key pair with a blank passphrase, which creates an unencrypted private key.
50-
2. Store your public and private keys in your GitHub repository as new 'Secrets' (under your repository settings), using the names `WPENGINE_PUBLIC_KEY` and `WPENGINE_PRIVATE_KEY` respectively. In theory, this replaces the need for encryption on the key itself, since GitHub repository secrets are encrypted by default.
50+
2. Store your public and private keys in your GitHub repository as new 'Secrets' (under your repository settings), using the names `WPENGINE_SSH_KEY_PRIVATE` and `WPENGINE_SSH_KEY_PUBLIC` respectively. In theory, this replaces the need for encryption on the key itself, since GitHub repository secrets are encrypted by default.
5151
3. Add the public key to your WP Engine production environment.
5252
4. Per the [WP Engine documentation](https://wpengine.com/git/), it takes about 30-45 minutes for the new SSH key to become active.

0 commit comments

Comments
 (0)