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.

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

[Feature Request] Custom Error Messages and Service Status Page #13

Open
jojoto opened this issue Aug 22, 2023 · 1 comment
Open

[Feature Request] Custom Error Messages and Service Status Page #13

jojoto opened this issue Aug 22, 2023 · 1 comment

Comments

@jojoto
Copy link

jojoto commented Aug 22, 2023

Hello there,

I would like to propose the addition of a feature that could greatly enhance user experience on Appteka's server. Currently, when the server encounters an error like a 502, users are left with minimal context about the issue. My suggestion is to implement a system that displays a personalized error message whenever an error occurs.

  • Custom Error Messages: Adding a simple and clear error message whenever an error code is encountered (e.g., 502 Bad Gateway) would provide users with valuable information about what's happening. This could significantly reduce user frustration and help them understand whether the issue is on their end or on the server's side.

  • Service Status Page: Additionally, it would be valuable to have a dedicated page displaying the status of various services utilized by Appteka. This could include integrating with well-known service status monitoring tools like Upptime, Uptime Kuma, etc. Having this status page would allow users to quickly check if the problem they're facing is specific to them or if it's a broader issue.

Thank you for considering this feature request. I look forward to your feedback and discussing the potential implementation further.

@solkin
Copy link
Owner

solkin commented Feb 12, 2024

Thank you for ideas! Service status page is really useful, I'll add it in the next updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants