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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -377,7 +377,7 @@ Stage and prod environments point at a specific git tag that is manually added.
377
377
378
378
1. When a PR that affects this app is merged to `main` in the sage-monorepo, wait for the [ci job](https://github.com/Sage-Bionetworks/sage-monorepo/actions/workflows/ci.yml) to finish building and publishing images for the affected projects to GHCR.
379
379
2. Rerun the last [deploy-dev job](https://github.com/Sage-Bionetworks-IT/modeladexplorer-infra/actions/workflows/deploy-dev.yaml) and wait for the job to successfully update dev deployment. Deployment can be monitored in AWS console in AWS ECS.
380
-
3. Confirm that [dev site](https://modeladexplorer-dev.org/) shows changes from last merged PR.
380
+
3. Confirm that [dev site](https://dev.modeladexplorer.org/) shows changes from last merged PR.
381
381
382
382
## Staging Deployment
383
383
@@ -394,7 +394,7 @@ Stage and prod environments point at a specific git tag that is manually added.
394
394
5. Merge PR. Wait for [deploy-dev job](https://github.com/Sage-Bionetworks-IT/modeladexplorer-infra/actions/workflows/deploy-dev.yaml) to successfully update dev deployment. Deployment can be monitored in AWS console in AWS ECS.
395
395
6. Create PR in this repo **to merge dev into the stage branch**.
396
396
7. Merge PR. Wait for [deploy-stage GHA job](https://github.com/Sage-Bionetworks-IT/modeladexplorer-v3/actions/workflows/deploy-stage.yaml) to successfully update staging deployment. Deployment can be monitored in AWS console in AWS ECS.
397
-
8. Confirm that [staging site](http://modeladexplorer-stage.org/) shows new version’s tag in the app footer.
397
+
8. Confirm that [staging site](http://stage.modeladexplorer.org/) shows new version’s tag in the app footer.
398
398
399
399
## Production Deployment
400
400
@@ -408,4 +408,4 @@ Stage and prod environments point at a specific git tag that is manually added.
408
408
- Push the tag: `git push upstream tag model-ad/release/v4.0.0`
409
409
3. Create a PR in this repo **to merge the stage branch into the prod branch**.
410
410
4. Merge PR. Wait for the [deploy-prod GHA job](https://github.com/Sage-Bionetworks-IT/modeladexplorer-v3/actions/workflows/deploy-prod.yaml) to successfully update prod deployment. Deployment can be monitored in AWS console in AWS ECS.
411
-
5. Confirm that [production site](http://modeladexplorer-prod.org/) shows the same tag in the app footer as the staging site.
411
+
5. Confirm that [production site](http://prod.modeladexplorer.org/) shows the same tag in the app footer as the staging site.
0 commit comments