On Wed, Nov 27, 2019 at 08:44:15AM -0500, Neal Gompa wrote: > On Wed, Nov 27, 2019 at 3:06 AM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote: > > > > Hi. > > For long time, I plan to do something about > > https://status.fedoraproject.org/ > > > > I think that manual updates of this page does not reflect the capabilities of these century. Well, I think then we are doing a poor job of explaining what it is and how it works, or I am missing what capabilities you are wanting it to have? We deliberately wanted it to be a manual update process. It's for showing when we are aware of some problem and are already working on it. This allows people who didn't notice the issue to know it's happening and avoid lots of people reporting the same issue. It is also deliberately not in our infra (it runs in aws). > > > > My question is: do we want to go SasS way? I found > > https://www.statusdashboard.com/pricing > > which would cost us $99 per month. > > > > Or we want to maintain it in-house? > > The code of this specific service is open-source > > https://github.com/tomalessi/statusdashboard > > thou there are no commits for past few years. > > And there are some alternatives like: > > https://github.com/statusdashboard/statusdashboard > > > > Two actively maintained open source options are: > > * Staytus: https://staytus.co/ > > * Cachet: https://cachethq.io/ > > Either could be customized and ran somewhere fairly easily... I'm open to moving to some other application, just would like to know the requirements or advantages to doing so would be... The current "app" (really just some html and js) could be prettier. It could also organize things better (by SLE perhaps). What other features would folks like? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
