Correct TLS certificate filename in the container deployment docs. Fixes #5708

pull/34/head
Dave Page 2020-07-29 09:26:12 +01:00
parent a0893fe43b
commit 6fc6ec1cda
2 changed files with 3 additions and 2 deletions

View File

@ -51,7 +51,7 @@ connections.
When TLS is enabled, a certificate and key must be provided. Typically these
should be stored on the host file system and mounted from the container. The
expected paths are /certs/server.crt and /certs/server.key
expected paths are /certs/server.cert and /certs/server.key
**PGADMIN_LISTEN_ADDRESS**
@ -318,7 +318,7 @@ adjusted as appropriate to the specific deployment:
listen 443;
server_name _;
ssl_certificate /etc/nginx/server.crt;
ssl_certificate /etc/nginx/server.cert;
ssl_certificate_key /etc/nginx/server.key;
ssl on;

View File

@ -23,3 +23,4 @@ Bug fixes
| `Issue #4810 <https://redmine.postgresql.org/issues/4810>`_ - Fixed an issue where the user is not able to save the new row if the table is empty.
| `Issue #5490 <https://redmine.postgresql.org/issues/5490>`_ - Make the runtime configuration dialog non-modal.
| `Issue #5646 <https://redmine.postgresql.org/issues/5646>`_ - Ensure that RLS Policy node should be searchable using search object.
| `Issue #5708 <https://redmine.postgresql.org/issues/5708>`_ - Correct TLS certificate filename in the container deployment docs.