![]() Per the WP Engine documentation, it takes about 30-45 minutes for the new SSH key to become active.Add the public key to your target WP Engine environment.In theory, this replaces the need for encryption on the key itself, since GitHub repository secrets are encrypted by default. 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.The simplest method is to generate a key pair with a blank passphrase, which creates an unencrypted private key. Generate a new SSH key pair as a special deploy key.Defining environment variables in GitHub Actions.Set which branch in your repository you'd like to push to WP Engine. You shouldn't need to change this, but if you're using WP Engine's legacy staging, you can override the default and set to staging if needed. See below for SSH key usage.ĭefaults to production. Public SSH key of your WP Engine git deploy user. Private SSH key of your WP Engine git deploy user. ![]() ![]() Now that the remote and local repositories can interact seamlessly, you can continue to. View the pushed files on the remote Git repository to verify that the git remote add and push commands ran successfully. If you encounter a fatal error when running the command, you should choose a name for your new remote or rename or delete the existing remote with the name you want to use. That means you can add remote repositories for both production and staging. The name of the WP Engine environment you want to deploy to. Run the git remote add origin command from your local repository with the -set-upstream and the name of the active branch to push. The git remote add command allows you to add a remote to a Git repository. Every WP Engine install comes with a staging site and a production site. WPENGINE_ENVIRONMENT_NAME = "my-cool-site-production"Įnvironment Variables & Secrets Required Name
0 Comments
Leave a Reply. |