Configuration Properties

The file workspace of the JS Registry.
Default: $\{data.directory.location\}/jspackages.

The base URL of the JS Registry.

The root endpoint of the JS Registry.

Set to true if the JS Registry shall allow uploading of resources into the registry.
Default: true.

Set to true to allow the distribution of packages (required for npm compatibility).
Default: false.

Indicates whether the bundles.js, layer.js, and bundles.json endpoints use a cache (set to true in production environment).

Indicates if the classpath scanner only considers JAR resources and skips extracted resources for example inside classes directories.
Default: true.

Time in milliseconds between successive classpath scans.
Default: -1 (scan only once at startup).

The folder to be scanned for packages.
Default: the js folder.

The context relative URL to the scanned folder. It is used to calculate the location URLs.
Default: "", no location URLs are generated.

Filter to indicate which directories are included in the scan.
Default: "**" (all).

Filter to indicate which directories shall be excluded from scanning.
Default: sample/**,apps/**.

Time in milliseconds between successive directory scans.
Default: 5000.

Flag to indicate that distribution tar and zip files are generated during the package imports. This is only relevant if the registry is used together with npm.

Flag to indicate that the scanned packages are registered as files and the contents are not imported into the database.
If true, all packages are "uploaded" into the database.

The folder to be scanned for JAR or zip files, which contain packages that get imported.
Default: WEB-INF/bundle-import.

Time in milliseconds between successive scans.
Default: -1 (scan only once at startup).

Flag indicating whether only bundle metadata is imported (true) or whether bundles within archives are extracted and imported in full (false). The archives are deleted after full import.
Default: true.