joschrew

Hi, I recently came across recreating checksums for bagits and wanted to know if ocrd can do it. This way I came across this issue. I hope you don't mind...

Thanks for answering. > For `bag -Z` there is a problem with the chosen output directory – `DEST` does not get used (see above). In my tests it worked as...

I wondered if we already have written down something regarding the ocrd_network or processing server, what we could simply link there. I know we have the config-spec Triet wrote, but...

From my point of view this can be closed because of #964 and #951. I think I wrongly used the `fix` keyword in the #951 this is why it didn't...

How would you address the problem regarding getting the workspace to be processed to the processing-worker? Currently when running and using ocrd in docker the current directory is volume-mounted into...

I have started the process of addressing all comments but this will take a while. I think I'll add them step by step. I will report back if that is...

Thanks for your help/input. May last commit updated the submodules (-PR's) and now the core image used is build with core/Dockerfile instead of building separately

I don't think 774 and 664 solve the problem. Idea is the following: The log-files are created by root, e.g. when in the docker-image creation ocrd-resources are downloaded or any...

The problem is this: When the images are created the logfiles might be created as well. For example when a processor's image extends core and then calls ocrd core for...

I imagine a setup where workers (and processing server) are on different vm's. The workspace is shared through NFS so that every processor has access to the same files. Currently...