Server plugin configuration
Config | Title | Status |
---|---|---|
020-prefixes | Configure prefixes (namespaces) | Not installed |
authenticate | Protect entire server | Not installed |
cache | Configure caching of RDF inputs | Not installed |
config | Web-based configuration | Installed (linked) |
debug | Set options for development | Installed (linked) |
flint | Include Flint SPARQL Editor | Not installed |
https | Provide HTTPS | Not installed |
https_only | Configure the HTTPS server | Not installed |
localhost | Configure HTTP to stay on localhost | Not installed |
lod | Configure Linked Data (LOD) access | Not installed |
logging | Configure logging of HTTP traffic | Not installed |
network | Configure the HTTP server | Installed (modified) |
pengines | Configure Pengines access | Installed (modified) |
rdfpath | Configure location of the RDF (ontology) library | Not installed |
skin_fix_menu | Fix the position of the menu and search box | Not installed |
store | Configure persistent storage | Installed (linked) |
winpath | Configure location of external programs on Windows | Not installed |
zlib | Enable the use of compressed RDF data | Installed (linked) |
About this table
The table above shows available and installed configuration modules.
File in conf.d
are loaded into the server at startup time
and extend or modify the server. Example configuration files are located
in examples/conf.d
. Configuration files can be in several
states:
- Not installed
- The config file is not in
conf.d
and not loaded - Installed (linked)
- The config file appears in
conf.d
as a (symbolic) link to the example file. - Installed (copied)
- The config file appears in
conf.d
as an unmodified copy of the example file. - Installed (modified)
- The config file appears in
conf.d
as an modified copy of the example file. - Local
- The config file appears in
conf.d
, but not in the example directory.
The link in the left-column shows the full documentation of the file.
The documentation-page allows for opening the file in an editor if the
file is loaded and a connection is made from localhost
.
The web interface allows for changing the status of configuration
files if the user is logged in with administrative rights. A
configuration file is renamed to oldname.disabled
if
it is disabled while it has local modifications.