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
{{ message }}
Repository navigation
Commit d79c129
Browse filesBrowse the repository at this point in the historyBrowse files
--body "This PR synchronized the files of this repo with the source of truth files in doc-internal. The PR should automatically merge, if it doesn't please fix files in docs-internal so that the fix is applied to every docs-staging-x repo." \
# Fetches the 'DOCS_BOT_PAT_READPUBLICKEY' secret from Vault to pass to the docker build environment as --secret id=DOCS_BOT_PAT_READPUBLICKEY,src=$(cat DOCS_BOT_PAT_READPUBLICKEY)
# Fetches the 'DOCS_BOT_PAT_READPUBLICKEY' secret from Vault to pass to the docker build environment as --secret id=DOCS_BOT_PAT_READPUBLICKEY,src=$(cat DOCS_BOT_PAT_READPUBLICKEY)
Copy file name to clipboardExpand all lines: src/deployments/staging/README.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The dedicated review servers are deployed in a similar fashion that the staging
26
26
27
27
Each staging server requires its own `github/` repo in order to deploy to Moda in the form of `github/docs-staging-X` where X is the number of that staging server e.g. `github/docs-staging-0` or `github/docs-staging-1`.
28
28
29
-
The URLs of the staging servers also follow this pattern, `docs-staging-x.github.net`, e.g. `docs-staging-2.github.net`
29
+
The URLs of the staging servers also follow this pattern, `https://docs-staging-{{x}}.service.iad.github.net`, e.g. `https://docs-staging-2.service.iad.github.net`
30
30
31
31
With the exception of the first 2 which are our review servers:
32
32
@@ -37,10 +37,13 @@ Ideally there should always be enough staging servers for each developer on the
37
37
38
38
So we have 8 dedicated staging servers, `docs-staging-{2-9}`:
> [Developer VPN](https://thehub.github.com/security/security-operations/developer-vpn-access/) access is required to view a staging server. Initial set up takes some work, but connecting to it after it's configured is rather simple.
44
47
45
48
## How do staging deploys work from docs-internal?
46
49
@@ -60,7 +63,7 @@ sequenceDiagram
60
63
WF2->WF2: 1. Extracts SHA from `repository_dispatch` event <br />2. Updates `.env` in docs-staging-x with SHA value<br />3. Auto-merges the PR into docs-staging-x
61
64
WF2->MD: Auto-merge kicks off Moda deploy
62
65
MD->MD: Dockerfile build clones docs-internal code from SHA target set in `.env`
63
-
note over MD: Deployed to <br/> `docs-staging-X.github.net`
66
+
note over MD: Deployed to <br/> `https://docs-staging-{{x}}.service.iad.github.net`
64
67
```
65
68
66
69
Whenever a developer pushes code to a staging branch in `docs-internal`, e.g. `docs-staging-2`, a pipeline begins with the final result being a staging server running with the latest changes from that branch. See the above diagram, or read below for a textual explanation.
@@ -81,13 +84,14 @@ The pipeline is as follows:
81
84
82
85
1. The PR merge kicks off an automatic Moda deploy for the `docs-staging-X` server.
83
86
84
-
1. At build time, the [Dockerfile](./Dockerfile) clones the `SHA` from `docs-internal` and builds, runs, and deploys it to https://docs-staging-X.github.net which is only accessible behind the devvpn.
87
+
1. At build time, the [Dockerfile](./Dockerfile) clones the `SHA` from `docs-internal` and builds, runs, and deploys it to `https://docs-staging-{{x}}.service.iad.github.net` which is only accessible behind the [Developer VPN](https://thehub.github.com/security/security-operations/developer-vpn-access/).
85
88
86
89
## How do review server deploys work from docs-internal?
87
90
88
91
The process is very similar to the process in the previous section for staging servers. The differences are as follows:
0 commit comments