The purpose of this repository is to provide a straightforward method for both technical and non-technical users to deploy a clone of a WordPress page from https://info.qa.orcid.org/ and https://info.orcid.org/.
- Make all required updates on WordPress QA (https://info.qa.orcid.org/).
- Follow the QA Deployment steps described below once the updates are done and tested on WordPress.
- Follow the PROD Deployment steps described below once the updates are done and tested on qa.orcid.org.
- Follow the Rollback PROD Deployment if something goes wrong or a previous version is needed.
- Navigate to Clone And QA Deploy WordPress Post
- Click on "Run workflow"
Note:
TODO: Provide more info to users that might not know how to get the page id
from the wordpress page they want to publish.
-
Verify info.orcid.org clone on QA:
- Navigate to Clone And QA Deploy WordPress Post
- Click on "Run workflow"
- Select environment =
QA
and select the WordPress page that needs to be deployed (default is25163
)
-
Update the fallback S3 bucket:
- Verify the default machine is working as expected: navigate to
orcid.org?home-page-force=s3-a
. - Navigate to the GitHub action -- WIP ---
- Click on "Run workflow"
- Select environment =
prod-s3-b
and select the GitHub version to release.- Please verify the version to be deployed has already been checked and approved on QA.
- See all available versions here.
- Verify the default machine is working as expected: navigate to
-
Update the default S3 bucket:
- Verify the fallback machine is working as expected: navigate to
orcid.org?home-page-force=s3-b
. - Navigate to the GitHub action -- WIP ---
- Click on "Run workflow"
- Select environment =
prod-s3-a
and select the GitHub version to release.- Please verify the version to be deployed has already been checked and approved on QA.
- See all available versions here.
- Verify the fallback machine is working as expected: navigate to
-- WIP ---