You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
First of all thank you for your effort to provide such a lean and compact implementation of xSyncBrowser api server.
I noticed the base image you used was centurylink/ca-certs. According to the DockerHub page of that image, it was meant to be used as a base image for images that require certificate verification for out-bound SSL connections. xSync is a server if I read it correctly, so what functionality is it to require out-bound SSL connections? Is it the ACME-related certificate automation?
Another question is, the centurylink/ca-certs image you used has not been updated for a long time, and its CA cert list might probably be outdated. Shall we consider using another actively maintained ca-certs image instead?
The text was updated successfully, but these errors were encountered:
First of all thank you for your effort to provide such a lean and compact implementation of xSyncBrowser api server.
I noticed the base image you used was
centurylink/ca-certs
. According to the DockerHub page of that image, it was meant to be used as a base image for images thatrequire certificate verification for out-bound SSL connections
. xSync is a server if I read it correctly, so what functionality is it to require out-bound SSL connections? Is it the ACME-related certificate automation?Another question is, the
centurylink/ca-certs
image you used has not been updated for a long time, and its CA cert list might probably be outdated. Shall we consider using another actively maintainedca-certs
image instead?The text was updated successfully, but these errors were encountered: