Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Update status.fp.o SOP

Browse source 
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 <rlerch@redhat.com>
This commit is contained in:
Ryan Lercho 2022-06-16 13:54:12 +10:00 • committed by zlopez
parent 8d951ce2ab
commit 24af45c64e
1 changed files with 7 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

47
modules/sysadmin_guide/pages/status-fedora.adoc
View file

@ -28,14 +28,14 @@ our main infrastructure, in AWS.
It is based on an S3 bucket with the files, fronted by a CloudFront It is based on an S3 bucket with the files, fronted by a CloudFront
distribution for TLS termination and CNAMEs. distribution for TLS termination and CNAMEs.
The website is statically generated using Pelican on your local machine, The website is statically generated using Pelican then pushed to S3
and then pushed to S3. through a github action.
== Adding and changing outages == Adding and changing outages
=== Making Changes === 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. and view changes.
[arabic] [arabic]
@ -94,46 +94,13 @@ file into a different status directory in `content/`, and regenerate.
== Publishing == 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 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 devserver, push them to the main branch on github. This can be done
changes live with the command: directly, or via a Pull Request.
.... Once the main branch is updated on Github, a github action automatically
make upload 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 == Renewing SSL certificate