https://github.com/thisislawatts/wordpress-deployment-example

https://github.com/thisislawatts/wordpress-deployment-example

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/thisislawatts/wordpress-deployment-example
• Owner: thisislawatts
• Created: 2021-08-20T20:06:15.000Z (about 3 years ago)
• Default Branch: staging
• Last Pushed: 2021-08-26T16:55:17.000Z (about 3 years ago)
• Last Synced: 2024-06-12T19:05:00.487Z (5 months ago)
• Language: CSS
• Size: 45.9 KB
• Stars: 0
• Watchers: 2
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Overview

---

An example repository demonstrating automated deployment to multiple environments.

These environments are:

* [Production](https://lukes-example-site.onyx-sites.io/)

* [Preview/staging](https://lukes-example-site-preview.onyx-sites.io/)

* [Development](https://lukes-example-site-development.onyx-sites.io/)

There is a lightweight Gitflow being used here to co-ordinate releases. This requires

2 branches; `staging` and `production`.

Aims

---

* No steps outside of GitHub are required trigger or manage deployments

* Makes GitHub the source of truth for what has been deployed to the Staging and Production environments. The mapping would be

  * Default branch `staging` => [Preview/staging](https://lukes-example-site-preview.onyx-sites.io/)

  * Production branch `production` => [Production](https://lukes-example-site.onyx-sites.io/)

Proposed workflow for contributors

---

1. Developer raise PR from their feature branch against the `staging` branch.

2. Feature branch will be deployed to [Development] environment

3. After approval is received, the owning developer merges their PR into the [Preview/staging] branch

4. Changes to `staging` are deployed to the [Preview/staging] environment

5. (Optional) In GitHub, a PR is automatically generated to merge the default branch into the production branch. This is known as the Release PR.

6. An admin user **manually** merges a Release PR into the `production` branch.

7. Any changes merged to the `production` branch are automatically deployed to the `production` environment.