The prefix that is added to all URLs.
Base path for content files (e.g. images). Used in the player and in the editor.
Base path for content files (e.g. images) IN THE PLAYER. It MUST direct to a URL at which the content files for THE CONTENT BEING DISPLAYED must be accessible. This means it must include the contentId of the object! You can insert the contentId using the placeholder {{contentId}}.
Example: http://127.0.0.1:9000/s3bucket/{{contentId}}`
You can use this URL to load content files from a different server, e.g. S3 storage. Note that this only work for the player and not the editor.
The URL of the Content Hub that is used to query content.
If true, the content hub is enabled.
The URL of the Content Hub at which you can retrieve metadata
Time after which the content hub metadata is considered to be outdated in milliseconds. User-configurable.
Time after which the content type cache is considered to be outdated in milliseconds. User-configurable.
URL prefix for content user data (e.g. the user state where a user left off displaying H5P content)
A list of file extensions allowed for content files. Contains file extensions (without .) separated by whitespaces.
This is the version of the H5P Core (JS + CSS) that is used by this implementation. It is sent to the H5P Hub when registering there. Not user-configurable and should not be changed by custom implementations.
Path to the H5P core files directory.
Options that change the looks and behavior of H5P.
Lists of JavaScript and CSS files that are added to the editor or player. The URLs in the lists are directly appended to the list of core scripts or styles without any modifications.
If true, the fullscreen button will not be shown to the user.
Path to the downloadable H5P packages.
Optional
editorYou can specify which addons should be added to which library here.
The property name is the machine mame to which to add addons. The string array contains the machine names of addons that should be added.
Path to editor "core files"
If set to true, the content types that require a Learning Record Store to make sense are offered as a choice when the user creates new content. User-configurable.
The maximum character count of paths of content files allowed when exporting h5p packages. If files would be longer, paths are shortened.
Unclear. Taken over from PHP implementation and sent to the H5P Hub when registering the site. User-configurable.
This is the version of the PHP implementation that the NodeJS implementation imitates. Can be anything like 1.22.1 It is sent to the H5P Hub when registering there. Not user-configurable and should not be changed by custom implementations.
The URL called to fetch information about the content types available at the H5P Hub. User-configurable.
The URL called to register the running instance at the H5P Hub. User-configurable.
The number of milliseconds that code has until a single library is installed. If this time is exceeded the lock will be freed and the library installation has failed.
How long to wait until a lock is acquired when installing a single library.
The URL of the library files (= content types).
Optional
library(optional) You can set server-wide custom settings for some libraries by setting the values here. As far as we know, this is currently only supported by H5P.MathDisplay. See https://h5p.org/mathematical-expressions for more information.
A list of file extensions allowed for library files. (File extensions without . and separated by whitespaces.) (All extensions allowed for content files are also automatically allowed for libraries).
The list of content types that are enabled when enableLrsContentTypes is set to true. Not user-configurable.
The maximum allowed file size of content and library files (in bytes).
The maximum allowed file size of all content and library files in an uploaded h5p package (in bytes).
The Url at which the parameters of a piece of content can be retrieved
This is the name of the H5P implementation sent to the H5P for statistical reasons. Not user-configurable but should be overridden by custom custom implementations.
This is the version of the H5P implementation sent to the H5P when registering the site. Not user-configurable but should be overridden by custom custom implementations.
Optional
playerYou can specify which addons should be added to which library in the player here.
The property name is the machine mame to which to add addons. The string array contains the machine names of addons that should be added.
The Url at which content can be displayed.
Optional
proxyAllows settings a http(s) proxy for outgoing requests. No proxy will be used if left undefined (or the one specified in the HTTPS_PROXY environment variable).
The hostname of the proxy without any protocol prefix (e.g. only 10.1.2.3)
The port of the proxy, e.g. 8080.
Optional
protocol?: "http" | "https"The protocol to use to access the proxy. Can be left undefined if http is used.
If true, the instance will send usage statistics to the H5P Hub whenever it looks for new content types or updates. User-configurable.
If true, the H5P client is told to send data about users finished a content object to the server. (This is the custom H5P setFinished report, not an xAPI statement)
URL prefix for the finished URL (the URL to which requests are sent when the user has finished content)
Indicates on what kind of network the site is running. Can be "local", "network" or "internet". TODO: This value should not be user-configurable, but has to be determined by the system on startup. (If possible.)
The URL path of temporary file storage (used for image, video etc. uploads of unsaved content).
URL prefix for all AJAX requests