... | ... | @@ -12,11 +12,9 @@ clearly and simply announce downtimes and recovery. |
|
|
|
|
|
<!-- more in-depth procedure that may require interpretation -->
|
|
|
|
|
|
## Signaling an issue
|
|
|
## Modifying the site
|
|
|
|
|
|
TODO: document how to push updates to the dashboard
|
|
|
|
|
|
Issues are in `content/issues`. Expand.
|
|
|
Issues are in `content/issues`. TODO: Expand.
|
|
|
|
|
|
## Changing categories
|
|
|
|
... | ... | @@ -30,6 +28,34 @@ refers to one or more "system" that is affected by it. |
|
|
The logo lives in `static/logo.png`. Some colors are defined in
|
|
|
`config.yml`, search for `Colors throughout cState`.
|
|
|
|
|
|
## Uploading site to the static mirror system
|
|
|
|
|
|
The `status.torproject.org` site currently lives in the [static mirror
|
|
|
system](howto/static-component). Ideally, it would be built through automated, continuous
|
|
|
integration (and maybe GitLab pages), but that is not currently the
|
|
|
case. So, first, the website needs to be built locally, with this
|
|
|
simple command:
|
|
|
|
|
|
hugo
|
|
|
|
|
|
That will create a bunch of (mostly plain HTML) files in
|
|
|
`public/`. This then needs to be uploaded to the static source server
|
|
|
(currently `staticiforme`, but the canonical source is defined in
|
|
|
Puppet, in `modules/roles/misc/static-components.yaml`). This `rsync`
|
|
|
command should be enough:
|
|
|
|
|
|
rsync -rtP public/ anarcat@staticiforme.torproject.org:/src/status.torproject.org/static-site/public/
|
|
|
|
|
|
NOTE: there is a copy of the static site git repository there. Ignore
|
|
|
it, it's out of date but could be used to build the website in a pinch.
|
|
|
|
|
|
Then the new source material needs to be synchronized to the mirrors,
|
|
|
with:
|
|
|
|
|
|
sudo -u torwww static-update-component status.torproject.org
|
|
|
|
|
|
This requires membership to the `torwww` group.
|
|
|
|
|
|
## Pager playbook
|
|
|
|
|
|
<!-- information about common errors from the monitoring system and -->
|
... | ... | |