Better error messages 001
Better error messages save time for everyone :- ) Here're some possible improvements:
If Ty's app server fails to connect to PostgreSQL, show an admin friendly error about that, instead of a long stack trace and hundreds of "too many client" errors (see e.g. [install error] - PGSQL: too many clients already).
Make the search container's hostname configurable, and show admin friendly messages if not found or isn't running.
If Ty has been incorrectly configured to use both HTTPS and HTTP, show an admin friendly message about that, instead of just blank pages (mixed content errors, scripts won't load).
- 0 replies
- Progresswith handling this problem
- @KajMagnus marked this topic as Planned 2022-06-14 12:48:29.022Z.