We often need to restart services for upgrades, maintenance and other reasons.
A lot of projects now have a status page that is hosted outside of their infrastructure and allows their users to check if something is going on.
We need to set one of those up for Software Heritage.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T496 Create a Software Heritage status page external to our infra | ||
| Migrated | gitlab-migration | T498 document how to use the status page on intranet.s.o |
Some of the relevant actors:
As a first attempt, I've now mailed status.io engaging in their FOSS sponsoring program. We'll see how it goes.
The status.io FOSS sponsoring team replied saying yes.
An account has been created with credentials stored in the password store.
This is now done, even if only in embryonic state.
For more fancy we can add more geeky way of updating the status page, using the status.io API and whatnot.