DE EN EN (Google)

Hotfolder Plugin

The hotfolder is a special directory for easydb. Files in this directory will be automatically imported into easydb.

To configure a hotfolder on the user’s side, see collection. This article is about the administrator’s side of the hotfolder configuration. (Both sides are needed)

Serving of the working directory

The working directory, in which the hotfolder will be reachable must be served to users with operating system means so that users can put new files there. Normally this will be done by WebDAV. Other options like FTP or SMB are also possible but not described here.

Configuration of WebDAV

WebDAV requires an Apache web server connected in front of the Docker containers, as described in configuration of Apache2/HTTPS

First of all your should activate the Apache module

a2enmod dav_fs

The hotfolder directory should exist and be accessible by apache. To ensure the webserver has access to the folder, change the owner of the directory to www-data (valid for Debian Linux):

mkdir -p /media/hotfolder
chown www-data. /media/hotfolder

The following configuration is necessary for the working directory (/media/hotfolder as example). Some options in VirtualHost were removed to ensure this listing stays small enough.

<VirtualHost *:443>
    AliasMatch ^/upload(.*)$ /media/hotfolder$1
    <Location /upload>
        ProxyPass "!"
            Require all granted
            Require all denied
        DAV on
        Options -MultiViews
        ErrorDocument 404 "Not Found"
        ErrorDocument 500 "Internal Server Error"
        ErrorDocument 502 "Bad Gateway"
    <LocationMatch /upload/collection/[^/]+/[^/]+/.*>
        Require all granted
        DAV on
        Options -MultiViews
        ErrorDocument 404 "Not Found"
        ErrorDocument 500 "Internal Server Error"
        ErrorDocument 502 "Bad Gateway"

    ProxyPass /
    ProxyPassReverse /

easydb-server configuration

easydb-server creates one subdirectory inside the above mentioned working directory for each collection that is configured in the webfrontend to allow upload.

Access for the easydb-server container

To access the hotfolder inside the easydb-server-container you have to mount it into the container during its creation. In our example /media/hotfolder will be visible as the expected /hotfolder inside the container, and the container creation is done inside the easydb-typical start-script:

docker run -d -ti \
	--name easydb-server \
	--volume /media/hotfolder:/hotfolder \$SOLUTION

… only the volume line has been added. Some other lines are shown as orientation, but not all.

Server YAML configuration

Example Configuration:

  enabled: true
  directory: /hotfolder
    - type: windows_webdav
      url: \\\upload\collection
      separator: \
    - type: mac_finder
      separator: /
    - type: webdav
      separator: /

    - base.hotfolder

… placed into e.g. /srv/easydb/config/easydb-server.yml:

We assume that your easydb uses https.

Server YAML variables to configure the Hotfolder

Variable Type Required Description
hotfolder List No Parent element which contains the configuration for easydb’s hotfolder
enabled bool Yes If the Hotfolder is enabled on this Server (default: false)
directory string Yes Path of the local Hotfolder to check for files
urls List Yes List of URL Configurations:
⇨⇨type string Yes Type of the Hotfolder URL: one of "windows_webdav", "webdav_http"
⇨⇨url string Yes URL of the WebDAV Folder
⇨⇨separator string Yes Separator Token that is used in the URL (default: /)
delay int No Time in seconds between each check for new files in the Hotfolder (default: 10)
number_of_workers int No Number of Worker Instances, currently ignored, only one worker is implemented
upload_batches bool No true: upload the generated objects generated from files in the Hotfolder in batches; false: upload single objects (default: false)
upload_batch_size int No Number of Objects to be uploaded in the same batch (default: 10, ignored for upload_batches = false)

Frontend localization for URL types

The frontend localizations for different types of hotfolder URLs can be added to the localization files in server/base/l10n. For each type in urls, a new localization can be added:

"server.base.hotfolder.urls.type.<type>": "URL Type"

where <type> is the configured URL type.

The server already supports localizations for the following URL types: