^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The default configuration does not expose the website to the network.
-Of course this can be reconfigured in the .ini file. However exposing
-pserve/waitress to the Internet is not recommended. Use a reverse web
-proxy instead, or configure your webserver of choice to talk with
-PGWUI via WSGI.
+Of course this can be reconfigured in the .ini file. However,
+although it will work, exposing pserve/waitress to the Internet is not
+recommended. Use a reverse web proxy instead, or configure your
+webserver of choice to talk with PGWUI via WSGI.
`Nginx`_ is often the simplest, and best, choice for an
-Internet-facing web server. A useful reverse-proxy configuration to
-connect the default WSGI server to the Internet might be::
+Internet-facing, reverse proxy, web server. A useful reverse-proxy
+configuration to connect the default WSGI server to the Internet might
+be::
location / {
proxy_pass http://localhost:6543;
Configuring routing means changing the URL used to access a page.
Usually this is the part of the URL which comes after the domain, the
part after the *https://www.example.com* part. Alternatively, a full
-URL may be supplied for a route. This can be used to direct the user
+URL may be supplied as a route. This can be used to direct the user
to an external website.
PGWUI_Server comes with sensible defaults. Configuring routing
pgwui_common:templates/base.mak Common "background" items on all pages.
pgwui_common:templates/auth_base.mak Common "background" items on all
- pages requesting connection and login data.
+ pages requesting database connection and login information.
pgwui_logout:templates/logout.mak The logout page.