Arbitrary output directory

[frederik-f]

Dear all,

I was really happy to come across this tool, which I want to use in combination with paperless ngx. I could set it up via a docker compose file, with one limitation. Within the docker container, the scans are stored at arbitrary locations and not at /scans. Therefore the binding to the persistent volume is also not working.

My compose file looks like this:

https://github.com/manuc66/node-hp-scan-to

version: "3"

services:
node-hp-scan-to:
image: manuc66/node-hp-scan-to:master
container_name: node-hp-scan-to
hostname: paperless_ngx
environment:
- IP=192.168.178.5
- PATTERN="scan"_dd.mm.yyyy_hh:MM:ss
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
- RESOLUTION=300
volumes:
- path-on-my-drive/paperless-consume:/scan
restart: "unless-stopped"

I also tried to set the output directory with the -DIR variable with no effect. That is the output when starting the container:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/10-adduser

User uid: 1002
User gid: 100

s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
Starting
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
WARNING: No configurations found in configuration directory:/app/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
Using device ip: 192.168.178.5
Target folder: /tmp/scan-to-pcdkALjH
Temp folder: /tmp/scan-to-pcFbmMhA
Running iteration: 0 - errorCount: 0
Host destinations fetched: paperless_ngx
Re-using existing destination: paperless_ngx - /WalkupScanToComp/WalkupScanToCompDestinations/1c853515-b82e-1f08-b36c-84a93e2da133
Using: paperless_ngx
Waiting scan event for: /WalkupScanToComp/WalkupScanToCompDestinations/1c853515-b82e-1f08-b36c-84a93e2da133
Start listening for new ScanEvent

I would be really glad, if anybody could help me with this problem!

Best regards!
Frederik

[frederik-f]

Just tried out the latest version (image: manuc66/node-hp-scan-to:master) and the problem doesn't exist there anymore.