diff --git a/docs/en_US/release_notes_4_25.rst b/docs/en_US/release_notes_4_25.rst index c2f41889f..585bc023f 100644 --- a/docs/en_US/release_notes_4_25.rst +++ b/docs/en_US/release_notes_4_25.rst @@ -33,4 +33,5 @@ Bug fixes | `Issue #5646 `_ - Ensure that RLS Policy node should be searchable using search object. | `Issue #5708 `_ - Correct TLS certificate filename in the container deployment docs. | `Issue #5710 `_ - Fixed an issue when comparing the table with a trigger throwing error in schema diff. -| `Issue #5716 `_ - Fixed an issue where ajax call continues to fire even after disconnect the database server. \ No newline at end of file +| `Issue #5716 `_ - Fixed an issue where ajax call continues to fire even after disconnect the database server. +| `Issue #5724 `_ - Clarify some of the differences when running in server mode in the docs. \ No newline at end of file diff --git a/docs/en_US/server_deployment.rst b/docs/en_US/server_deployment.rst index 584403bf1..f80b0c4d8 100644 --- a/docs/en_US/server_deployment.rst +++ b/docs/en_US/server_deployment.rst @@ -8,6 +8,15 @@ pgAdmin may be deployed as a web application by configuring the app to run in server mode and then deploying it either behind a webserver running as a reverse proxy, or using the WSGI interface. +When deployed in server mode, there are two notable differences for users: + +* Users must login before they can use pgAdmin. An initial superuser account + is created when server mode is initialised, and this user can add additional + superusers and non-superusers as required. +* File storage is restricted to a virtual root directory for each individual + user under the directory configured using the ``STORAGE_DIR`` configuration + parameter. Users do not have access to the complete filesystem of the server. + The following instructions demonstrate how pgAdmin may be run as a WSGI application under ``Apache HTTPD``, using ``mod_wsgi``, standalone using ``uWSGI`` or ``Gunicorn``, or under ``NGINX`` using using ``uWSGI`` or ``Gunicorn``.