You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,16 +19,23 @@ Only keep lines below that describe this change, then delete the rest.
19
19
20
20
Please provide screenshots / animations for any change that involves the UI. Please provide animations to demonstrate user interaction / behavior changes
21
21
22
-
## How Has This Been Tested?
22
+
## Testing on your branch
23
23
24
-
Please describe the manual tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
24
+
Please describe how to test and/or verify your changes. Provide instructions so we can reproduce. Please also provide relevant test data as necessary. These instructions will be used for QA testing below.
25
25
26
26
-[ ] Test A
27
27
-[ ] Test B
28
28
29
-
## Checklist:
29
+
## Checklist
30
30
31
31
-[ ] I have performed a self-review of my own code
32
32
-[ ] I have reviewed the title/description of this PR which will be used as the squashed PR commit message
33
33
-[ ] I have commented my code, particularly in hard-to-understand areas
34
34
-[ ] I have added tests that prove my fix is effective or that my feature works
35
+
36
+
## qa.languageforge.org testing
37
+
38
+
Reviewers: add/replace your name below and check the box to sign-off/attest the feature works as expected on qa.languageforge.org
Copy file name to clipboardExpand all lines: README.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,10 +166,6 @@ After a minute or two, your source or test changes should be applied and you sho
166
166
167
167
1.`make dev` will start the app in development mode, i.e. changes to source code will immediately be reflected in the locally running app.
168
168
169
-
### Building for deployment
170
-
171
-
1. Refer to `/.github/workflows/build-and-deploy-images.yml` for production build commands and `/.github/workflows/deployment-staging.yml` for staging build commands.
172
-
173
169
### Visual Studio Code ###
174
170
175
171
Visual Studio Code is a simple, free, cross-platform code editor. You can download VS Code from [here](https://code.visualstudio.com/).
@@ -237,24 +233,26 @@ To debug the tests:
237
233
- To debug in VSCode, select the "Node debugger" debug configuration and run it.
238
234
239
235
## Application deployment ##
240
-
Language Forge is built to run in a containerized environment. For now, Kubernetes is the chosen runtime platform. Deployments are not currently automated and must be manually run with the appropriate credentials or from within our CD platform, TeamCity at this time. Deployment scripts for k8s can be found in `docker/deployment`
236
+
Language Forge is built to run in a containerized environment. For now, Kubernetes is the chosen runtime platform. Deployments are automated under the right circumstances using GitHub Actions.
241
237
242
238
### Staging (QA) ###
243
-
Staging deployments can be run with `VERSION=<some-docker-tag-or-semver> make deploy-staging`.
239
+
Staging deployments can be manually run with `VERSION=<some-docker-tag-or-semver> make deploy-staging`.
244
240
245
241
Current workflow:
246
-
1. merge commits into or make commits on `develop` branch
247
-
1. this will kick off the GHA (`.github/workflows/deployment-staging.yml`) to build, publish the necessary images to Docker Hub (https://hub.docker.com/r/sillsdev/web-languageforge/tags) and deploy to the staging environment.
242
+
1. merge PR into or make commits on `develop` branch
243
+
1. this will kick off the GHA (`.github/workflows/staging.yml`) to build, test and publish the necessary images to Docker Hub (https://hub.docker.com/r/sillsdev/web-languageforge/tags) and deploy this code to the staging environment at https://qa.languageforge.org
248
244
249
245
### Production ###
250
-
Production deployments can be run with `VERSION=<some-docker-tag-or-semver> make deploy-prod`.
246
+
Production deployments can be manually run with `VERSION=<some-docker-tag-or-semver> make deploy-prod`.
251
247
252
248
Current workflow:
253
249
1. merge from `develop` into `master`
254
250
1. "Draft a new release" on https://github.com/sillsdev/web-languageforge/releases with a `v#.#.#` tag format
255
251
1. "Publish" the new release
256
-
1. this will kick off the GHA (`.github/workflows/build-and-deploy-images.yml`) to build and publish the necessary images to Docker Hub (https://hub.docker.com/r/sillsdev/web-languageforge/tags)
257
-
1. then the deployment scripts can be run either manually or via the TeamCity deploy job
252
+
1. this will kick off the GHA (`.github/workflows/production.yml`) to build, test and publish the necessary images to Docker Hub (https://hub.docker.com/r/sillsdev/web-languageforge/tags) and deploy this code to the production environment at https://languageforge.org
253
+
254
+
### Revert ###
255
+
Various tagged images are maintained in Docker Hub. If you need to revert to a previous version, you can do so by running the deployments scripts with the appropriate permissions or utilizing the Kubernetes UI to change the image of a deployment at any time.
258
256
259
257
### Backup/Restore ###
260
258
Backups will be established automatically by LTOps and utilized by LF through the `storageClassName` property in a Persistent Volume Claim. This storage class provided by LTOps establishes both a frequency and retention for a backup. Any time a restoration is needed, the LF team will need to coordinate the effort with LTOps. The process of restoring from a point in time will require the application be brought down for maintenance. The process will roughly follow these steps:
0 commit comments