From 24af45c64ec837d2b37c9566ea4f03e720d111e0 Mon Sep 17 00:00:00 2001 From: Ryan Lerch Date: Thu, 16 Jun 2022 13:54:12 +1000 Subject: [PATCH] Update status.fp.o SOP Update the status.fp.o SOP, removing the details on manually updating S3. It now is done automatically via github actions Signed-off-by: Ryan Lerch --- .../sysadmin_guide/pages/status-fedora.adoc | 47 +++---------------- 1 file changed, 7 insertions(+), 40 deletions(-) diff --git a/modules/sysadmin_guide/pages/status-fedora.adoc b/modules/sysadmin_guide/pages/status-fedora.adoc index 4a55c14..9313033 100644 --- a/modules/sysadmin_guide/pages/status-fedora.adoc +++ b/modules/sysadmin_guide/pages/status-fedora.adoc @@ -28,14 +28,14 @@ our main infrastructure, in AWS. It is based on an S3 bucket with the files, fronted by a CloudFront distribution for TLS termination and CNAMEs. -The website is statically generated using Pelican on your local machine, -and then pushed to S3. +The website is statically generated using Pelican then pushed to S3 +through a github action. == Adding and changing outages === Making Changes -Before pushing changes live to S3, use the Pelican's devserver to stage +Before pushing to the Github Repository, use the Pelican's devserver to stage and view changes. [arabic] @@ -94,46 +94,13 @@ file into a different status directory in `content/`, and regenerate. == Publishing -Only members of sysadmin-main and people given the AWS credentials can -update the status website. - -=== Initial Configuration for Publishing - -[arabic] -. First, install the AWS command line tool with: -+ -.... -sudo dnf install aws-cli -.... -. Grab `ansible-private/files/aws-status-credentials` and store in -`~/.aws/credentials`. -. Run: -+ -.... -aws configure set preview.cloudfront true -.... - -=== Publishing changes live - Once you are satisfied with your changes and how they look on the -devserver, and they have been committed to Git, and push the built -changes live with the command: +devserver, push them to the main branch on github. This can be done +directly, or via a Pull Request. -.... -make upload -.... +Once the main branch is updated on Github, a github action automatically +pushes the changes live to https://status.fedoraproject.org -Note that this command only updates content changes (i.e. adding / -moving outages) - -=== Publishing theme changes - -If your changes involve changes to the theme, run the following command -to upload everything (content and theme changes) to the live server: - -.... -make upload-theme -.... == Renewing SSL certificate