Project

General

Profile

Actions

Feature #6124

closed

Implement "Status" Site to communicate during outages

Added by Stephen Real over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Stephen Real
Category name:
-
Target version:
Start date:
2016-10-04
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

We have discussed the idea of creating a status site on separate platform in order to inform users of Commons status during outages. Let's create the site and implement that mechanisms to point to it. Once that's in place we can develop protocols for maintaining the information on the site and develop a promotional campaign to announce to users that it exists and how to use it.


Files

Actions #1

Updated by Matt Gold over 7 years ago

  • Tracker changed from Bug to Feature
  • Status changed from New to Assigned
  • Assignee set to Boone Gorges

I think that a very basic wp.com site with a status update would do.

Let us know whether you need models, Boone.

We will create a shortlink for it -- cuny.is/status -- when we have it.

Actions #2

Updated by Boone Gorges over 7 years ago

Here's what I've done:

- Created a cunyacademiccommons account at wordpress.com, using the address.
- Created https://commonsstatus.wordpress.com/ with that account, and did some basic configuration of the site.
- Modified our maintenance splash page to include a link.
- Added a custom error page for "Error connecting to the database" errors, which also contains a link to the status site.

See attached screenshots.

I've also reached out to Lihua about the possibility of custom Apache error pages, which would come into play for generic Apache errors (unrelated to MySQL).

I believe the next steps are for Stephen and the community team:
- Develop a protocol for who should post to the status blog, and when.
- Develop a protocol for sharing the wordpress.com credentials. I have them, and I can share them however the team thinks is best.
- Ensure that the folks with the keys to the social media streams are aware of the blog.

I've put this into the 1.9.30 milestone because that's when the custom maintenance and db-error.php pages will ship.

Actions #3

Updated by Matt Gold over 7 years ago

thanks for your work on this, Boone.

Actions #4

Updated by Boone Gorges over 7 years ago

After follow-up from Lihua, I've added a custom 500 error page: https://github.com/cuny-academic-commons/cac/commit/c7cce74fd13aa1242469a23a90aceda690f7d5f2

Actions #5

Updated by Matt Gold over 7 years ago

thanks, Boone -- that looks great.

Actions #6

Updated by Boone Gorges over 7 years ago

  • Target version changed from 1.9.30 to 1.9.31
Actions #7

Updated by Boone Gorges over 7 years ago

  • Status changed from Assigned to Resolved
  • Target version changed from 1.9.31 to 1.9.30

Whoops - I should keep this in 1.9.30, because that's when the code shipped to the Commons. Stephen, if you need new Redmine tickets for the non-code-related items described above, could you create them? Or perhaps we can decide on that stuff through the Commons group.

Actions

Also available in: Atom PDF