Make network error pages more informative, user-friendly, and Cantus Ultimus specific
Open
Enhancement
first good issue
Low Priority
Public Website
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 4
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
related to #424, do we want to give nginx pages to display for 400 and 500 errors? we could add those to the cantus-staticpages repo and redirect in nginx. Or leave it bare and just delete the current 500 location block
Contributor guide
No contributing guide indexed for this repository
Research direction
Read related issue #424 and inspect the current nginx configuration, especially the 500 location block. Compare the two stated options: adding 400 and 500 pages to the cantus-staticpages repository and redirecting to them, or removing the existing 500 block; done means the chosen approach provides Cantus Ultimus-specific error pages or a deliberate bare response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100