@@ -137,8 +137,8 @@ Triggering preprocessing and registration via pushing to the redis queues is ver
``Ingestor`` can work in two modes:
- Default: Exposing a simple ``/`` endpoint, and listening for ``POST`` requests containing ``data`` with either a Browse Report JSON or a string with path to the object storage with product to be ingested. It then parses this informatio and internally puts it into configured redis queue (preprocess or register).
- Alternative: Listening for newly added Browse Report files on a configured path on a file system via ``inotify``.
- Default: Exposing a simple ``/`` endpoint, and listening for ``POST`` requests containing ``data`` with either a Browse Report XML or a string with path to the object storage with product to be ingested. It then parses this information and internally puts it into configured redis queue (preprocess or register).
- Alternative: Listening for newly added Browse Report or Availability Report files on a configured path on a file system via ``inotify``.
These Browse Report files need to be in an agreed XML schema to be correctly handled.
``Sftp`` service enables a secure access to a configured folder via sftp, while this folder can be mounted to other vs services. This way, ``Ingestor`` can listen for newly created files by the sftp access.
If the filedaemon alternative mode should be used, ``INOTIFY_WATCH_DIR`` environment variable needs to be set and a ``command`` used in the docker-compose.<stack>.ops.yml for ``ingestor`` service needs to be set to ``python3 filedaemon.py``:
