|Did you know ...||Search Documentation:|
|Pack prologmud_samples -- prolog/prologmud_sample_games/config-enabled-swish/README.md|
At startup, SWISH reads *.pl files from the directory
The *.pl are loaded using ensure_loaded/1 in alphabetical order.
config-available provides skeleton files for common
configuration settings. These files may be linked from or copied to
The following authentication scenarios may be configured
auth_http_always.pl, any access to SWISH requires authentication. This config module is not compatible with one of the other auth_* configuration modules.
rlimit.plsupports limiting the memory (and optionally other resources) that can be used by the SWISH server.
A number of configuration modules contribute to enabling collaboration support such as managing users and get notifications.
email.plneeds to be installed to enable notifications using mail. This module needs to be configured for contacting a mail gateway. Email also requires the GIT submodule pack/smtp to be checked out.
user_profile.plneed to be enabled to send notification and manage user profiles. The latter also requires the GIT submodule pack/profile to be checked out.
network.plis often needed to tell swish about the public HTTP host and port at which it is accessible. This is notably the case if proxies or tunnels are involved.
r_serve.plconfig file provides R integration. See
r_serve.plfor how to setup R itself for use with SWISH. R also requires the GIT submodule pack/rserve_client to be checked out and configured using
debug.plprovides several hints and tools to simplify server-side debugging of SWISH.
logging.plconfigures the creation of HTTP and Pengine log files.