Doc update from @acidtib in https://github.com/basecamp/kamal-site/pull/174
This commit is contained in:
@@ -50,8 +50,9 @@ proxy:
|
||||
# Custom SSL certificate
|
||||
#
|
||||
# In some cases, using Let's Encrypt for automatic certificate management is not an
|
||||
# option, or you may already have SSL certificates issued by a different
|
||||
# Certificate Authority (CA). Kamal supports loading custom SSL certificates
|
||||
# option, for example if you are running from host than one host. Or you may already
|
||||
# have SSL certificates issued by a different Certificate Authority (CA).
|
||||
# Kamal supports loading custom SSL certificates
|
||||
# directly from secrets.
|
||||
#
|
||||
# Examples:
|
||||
@@ -60,6 +61,11 @@ proxy:
|
||||
# ssl: # Enable custom SSL
|
||||
# certificate_pem: CERTIFICATE_PEM
|
||||
# private_key_pem: PRIVATE_KEY_PEM
|
||||
#
|
||||
# ### Notes
|
||||
# - If the certificate or key is missing or invalid, kamal-proxy will fail to start.
|
||||
# - Always handle SSL certificates and private keys securely. Avoid hard-coding them in deploy.yml files or source control.
|
||||
# - For automated certificate management, consider using the built-in Let's Encrypt integration instead.
|
||||
|
||||
# SSL redirect
|
||||
#
|
||||
|
||||
Reference in New Issue
Block a user