Closed ghost closed 1 year ago
Isn’t that a pretty extraordirary case?
@samhocevar @chclaus Is this something which should Dave handle itself?
Hej,
I think we shouldn't rely on the configuration-schema of other specific tools.
@nudeldudel furthermore I think your container setup could use a change. In my opinion each container should serve exactly one service. So I think you could improve your setup if you divide both applications into separate containers. As potential fix for your needs, you could create a kind of init-container which creates application specific user stores and mount them into the application containers.
@nudeldudel this ist just an example to create the user yaml structure out of your pureftpd password file
cat /etc/pure-ftpd/pureftpd.passwd | awk '{split($0,a,":"); printf " %s:\n password: \"%s\"\n subdir: \"%s\"\n", a[1], a[2], a[6] }'
Joerg
I agree that puredb is not a useful interchange format and is far too specific for Dave to support. Generating the user databases for both services from a common source seems like the better approach.
Is there any chance to alternate the user management to a puredb file by pure ftp. Therefore, the config.yml should be obsolete.
The case-scenario is a docker-container, which conclude pureftp and dave to a simple data storage especial for document-scanning.