Closed BlackHoleFox closed 3 months ago
[!IMPORTANT]
Review skipped
Auto reviews are limited to specific labels.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yaml
file in this repository. To trigger a single review, invoke the@coderabbitai review
command.You can disable this status message by setting the
reviews.review_status
tofalse
in the CodeRabbit configuration file.
A new read-only entry for SSL has been added to the map
structure in the proxy-manager/config.yaml
file, enhancing the configuration to support SSL settings securely without changeable access.
Files | Change Summary |
---|---|
proxy-manager/config.yaml |
Added a read-only entry for ssl under map |
In the land of config files and code, A new entry blossoms, SSL bestowed. Secure and steadfast, it stands in place, Read-only, protecting the network's grace. 🎉✨🐇
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.
Proposed Changes
Proposed here is the ability for the NGINX Proxy Manager addon to reuse an existing SSL certificate created and managed outside of its context, such as with HA's Lets Encrypt addon. The intention is people will use their own SSL directives in custom server blocks to access the cert since upstream nginx-proxy-manager doesn't support on-disk certs currently. Whenever it does though no changes would be needed here.
Why is this needed instead of using the built-in certificate generation? I have multiple addons in HA that share a certificate directory and I don't want to issue multiple certificates for services on the same hardware/OS.
Related Issues
didn't see any
Summary by CodeRabbit