-
Notifications
You must be signed in to change notification settings - Fork 63
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.
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
Inform users we intentionally shut down cgit instead of 500 #3595
Comments
Agree. If we decide to keep cgit long-term (I still keep joking about forgejo), we should prepare a simple static page saying that the server is down intentionally, and serve it when we do that chmod -x workaround. Or somehow else tweak the error message. |
In the meantime, maybe we can use frontend warning that we typically use for announcing outages? |
Jokes aside; driving our own "read-only" instance wouldn't make sense, but having a namespace in the Fedora official forge doesn't sound weird at all to me (of course, considering infra folks are OK to hold Copr's traffic at that point in time).
Sounds good. Is this a duplicate to #3591? |
in past 2 days we got 2 notifications on matrix about broken cgit. Since https://copr-dist-git.fedorainfracloud.org/cgit throws 500, users don't know it's intentional. Also this is not the first time we have problems with cgit and we shit it down, so this can be useful in the future
The text was updated successfully, but these errors were encountered: