From 8826990bd596e5a8058527ea520fbc10009cb41b Mon Sep 17 00:00:00 2001 From: David Humphrey Date: Mon, 17 Jan 2022 18:27:31 -0500 Subject: [PATCH] Update docs/architecture.md Co-authored-by: Josue --- docs/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture.md b/docs/architecture.md index a524cd26a1..5526ce0b4a 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -81,7 +81,7 @@ In development, we use a test PHP-based SAML Identity Provider to test against. ### Autodeployment Server -Our release infrastructure is built primarily on GitHub Actions, see `.github/workflows/release.yml`. However, we also host our own build service at `tools/autodeployment`. When a [Release is created](release.md), the autodeployment server receives a webhook event from GitHub. We use this to trigger a new build and deploy it when complete. the build script that gets run is at `tools/autodeployment/deploy.sh`, which does a green/blue style of deployment (i.e., keep one version running while you build a new one, swap them when ready). +Our release infrastructure is built primarily on GitHub Actions, see `.github/workflows/release.yml`. However, we also host our own build service at `tools/autodeployment`. When a [Release is created](release.md), the autodeployment server receives a webhook event from GitHub. We use this to trigger a new build and deploy it when complete. The build script that gets run is at `tools/autodeployment/deploy.sh`, which does a green/blue style of deployment (i.e., keep one version running while you build a new one, swap them when ready). The autodeployment server is run outside of Docker, since it manages our docker containers. It has an API available at (production) and (staging), and build logs are available at `/deploy/status/log`.