The settings for the disk filesystem. This filesystem is accessible on /
via HTTP. This filesystem can only be accessed for reading via HTTP. Writing to and deleting from the filesystem is possible via the API.
Path to a directory on disk. It will be exposed on /
for reading.
Relative paths are interpreted relative to where the datarhei Core binary is executed.
By default it is set to ./data
.
The maximum amount of data that is allowed to be stored in this filesystem. The value is interpreted as megabytes. A 507 Insufficient Storage
will be returned if you hit the limit. Use a value equal to or smaller than 0
to not impose any limits. Then all the available space on the disk is the limit.
By default no limit is set, i.e. a value of 0
.
Set this value to true
in order to enable the cache for the disk. The cache is an LRU cache, i.e. the least recently accessed files in the cache will be removed in case the cache is full and a new file wants to be added.
By default the value is set to true
.
Limit for the size of the cache in megabytes. A value of 0 doesn't impose any limit. The limit will be the available memory.
By default no limit is set, i.e. a value of 0
.
Number of seconds to keep a file in the cache.
By default this value is set to 300
seconds.
Limit for the size of a file to be allowed to be put in the cache in megabytes.
By default this value is set to 1
megabyte.
A list of file extensions to cache, e.g. [".ts", ".mp4"]
. Leave the list empty in order to cache all files. Use a space-separated list of extensions for the environment variable, e.g. .ts .mp4
.
By default the list is empty.
A list of file extensions not to cache, e.g. [".m3u8", ".mpd"]
. Leave the list empty in order to block no extension. Use a space-separated list of extensions for the environment variable, e.g. .m3u8 .mpd
.
By default the manifest files for HLS and DASH are blocked from caching, i.e. [".m3u8", ".mpd"].
The settings for the in-memory filesystem. This filesystem is accessible on /memfs
via HTTP. This filesystem can only be accessed via HTTP. Writing to and deleting from the filesystem can be restricted by HTTP basic auth.
Set this value to true
in order to enable basic auth for PUT
, POST
, and DELETE
operations on /memfs. Read access (GET
, HEAD
) is not restricted. If enabled, you have to define a username and a password.
It is highly recommended to enable basic auth for write operations on /memfs
.
By default this value is set to false
.
Username for Basic-Auth of /memfs. This has to be set if basic auth is enabled.
By default this value is not set, i.e. an empty string.
Password for Basic-Auth of /memfs. This has to be set if basic auth is enabled.
By default this value is not set, i.e. an empty string.
The maximum amount of data that is allowed to be stored in this filesystem. The value is interpreted as megabytes. A 507 Insufficient Storage
will be returned if you hit the limit. Use a value equal to or smaller than 0
to not set any limits. The limit will be the available memory.
By default no limit is set, i.e. a value of 0
.
Whether to automatically remove the oldest files if the filesystem is full.
By default this value is set to false
.
The settings for the S3 filesystem. This filesystem is accessible on the configured path via HTTP. This filesystem can only be accessed via HTTP. Writing to and deleting from the filesystem can be restricted by HTTP basic auth.
Any S3 compatible service can be used, e.g. Amazon, Minio, Backblaze, ...
Available as of version 16.12.0
The name for this storage. The name will be used in placeholders, e.g. {fs:aws}
, and for accessing the filesystem via the api, e.g. /api/v3/fs/aws
. The name memfs
is reserved for the in-memory filesystem.
By default this value is not set, but is required.
The path where the filesystem will be mounted in the HTTP server. It needs to be an absolute path. A mountpoint is required.
By default this value is not set, but is required.
Set this value to true
in order to enable basic auth for PUT
, POST
, and DELETE
operations on the configured mountpoint. Read access (GET
, HEAD
) is not restricted. If enabled, you have to define a username and a password.
It is highly recommended to enable basic auth for write operations on the mountpoint.
By default this value is set to false
.
Username for Basic-Auth of the configured mountpoint. This has to be set if basic auth is enabled.
By default this value is not set, i.e. an empty string.
Password for Basic-Auth of the configured mountpoint. This has to be set if basic auth is enabled.
By default this value is not set, i.e. an empty string.
The endpoint for the S3 storage. For Amazon AWS S3 it would be e.g. s3.amazonaws.com
. Ask your S3 storage provider to the necessary credentials.
By default this value is not set, i.e. an empty string.
Your access key ID for the S3 storage. Ask your S3 storage provider to the necessary credentials.
By default this value is not set, i.e. an empty string.
Your secret access key for the S3 storage. Ask your S3 storage provider to the necessary credentials.
By default this value is not set, i.e. an empty string.
The name of the bucket you want to use. If the bucket does not exist already it will be created.
By default this value is not set, i.e. an empty string.
Identifier for the region the storage is located, e.g. eu
, us-west1
, ... . If your S3 storage provider doesn't support regions, leave this field empty.
By default this value is not set, i.e. an empty string.
Whether to use HTTPS or HTTP. It is strongly recommended to enable this setting.
By default this is set to false
.
Settings for accessing the available storage types. The storages are accessible via HTTP, mounted to different paths.
Path to a file with the mime-type definitions. This is a file with the MIME types has one MIME type per line followed by a list of file extensions (including the "."). Files served from the storages will have the matching mime-type associated to it.
Example:
Relative paths are interpreted relative to where the datarhei Core binary is executed.
Default: ./mime.types
Define a list of allowed CORS origin for accessing the storages.
By default it contains the only element *
, allowing access from anywhere.
The disk storage is mounted at /
via the HTTP server.
The memory storage is mounted at /memfs
via the HTTP server.
The S3 storage is mounted at the configured path via the HTTP server.
S3 storage is available as of version 16.12.0