-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appwrite Doctor status for appwrite-worker-certificates #928
Labels
enhancement
New feature or request
Comments
We could add a section containing all requirements for generating a certificate and validate them:
Then we can maybe list all the certificates we have stored, with:
@TorstenDittmann @christyjacob4 @lohanidamodar do you have anything to add? |
@eldadfux Looks like you have covered everything. 馃挭 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃殌 Feature
Add debug & status info for
appwrite-worker-certificates
containers in Appwrite Doctor.Have you spent some time to check if this issue has been raised before?
Yes. Spoke briefly with @eldadfux about it on Discord as well.
Have you read the Code of Conduct?
Yes.
Pitch
LetsEncrypt calls can fail inside appwrite-worker-certificates containers, but Appwrite will continue to run and Appwrite Doctor will report that everything is okay regardless of success/failure. It would be great if Appwrite Doctor could communicate certificate errors when they occur.
It may also be useful if Appwrite Doctor could summarize certificate configuration and status. For example:
_APP_ENV=development
, determine whether the current configuration would succeed if we switched the value to production?The text was updated successfully, but these errors were encountered: