Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Streamline infrastructure status update system #29

Open
2 tasks
renoirb opened this issue Jan 9, 2015 · 2 comments
Open
2 tasks

Streamline infrastructure status update system #29

renoirb opened this issue Jan 9, 2015 · 2 comments
Labels
0 - Pending prioritization critical required to meet policies Unplanned wontfix Workflows

Comments

@renoirb
Copy link
Member

renoirb commented Jan 9, 2015

  • Analyze how to ease status update
  • Minimize steps to update, fan out to other systems: IRC, Twitter, Status page, etc.
@renoirb renoirb self-assigned this Jan 9, 2015
@renoirb
Copy link
Member Author

renoirb commented Jan 9, 2015

Suggestion.

As a user, what is annoying is an error page when we save something after a contribution. Losing last minutes of work.

While most of what a sysadmin do is to reload services without killing them. But some other services doesn’t support reload and we therefore need to restart completely. Not to forget when an underlying system breaks without human intervention, we might want to be notified.

How about we set in place an asynchronous notification system within our pages?

Making this feature might be not be too hard to do:

  • Create notification alert markup and styling
  • Have a small JavaScript listener to a WebSocket server
  • Make a WebSocket postMessage client taking two parameters
  • A message could contains at least the following: Where (e.g. wiki), message, link to the status page post

@renoirb renoirb assigned renoirb and unassigned renoirb Jan 9, 2015
@renoirb
Copy link
Member Author

renoirb commented Jan 16, 2015

Might be related to #72

@renoirb renoirb removed their assignment Sep 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - Pending prioritization critical required to meet policies Unplanned wontfix Workflows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@renoirb