Cryptomator and DocFetcher


I’ve put a portable version of DocFetcher (file system indexing program) in a Cryptomator vault and I want to index a directory located in another Cryptomator vault. The portable version of DocFetcher stores the index files in the same directory as the portable version of DocFetcher is located (so it is running from and writing to the cryptomator vault). When trying to index the cryptomator directory with the portable version of DocFetcher, I get the error (in logfile DocFetcher): Pro
app.portable=true Runtime Environment
os.arch=amd64 10
at java.base/ Source)
at java.base/ Source)
at java.base/ Source)
at java.base/java.nio.channels.FileChannel.tryLock(Unknown Source)
at org.apache.lucene.index.IndexWriter.(
at com.docfetcherpro.model.IndexActor.index1(IndexActor.scala:77)
at com.docfetcherpro.model.IndexActor.$anonfun$index$1(IndexActor.scala:18)
at com.docfetcherpro.util.MethodActor$$anon$
at com.docfetcherpro.util.MethodActor$$anon$

Has anyone managed to use DocFetcher in a Cryptomated directory? And if so - did you encounter and overcome this problem?

I don’t know if this is a Cryptomator or a DocFetcher problem…


You might be the first person to have ever thought to try something like this.

No idea how to Help. best of luck.

I use doc fetcher also but never thought to put it in a Vault and mine not portable.

I have thought about making it portable though because I do have more than one computer that I would like to use the database with.

Thanks for your support!

For portability reasons it is very obvious to be able to put at least the index-files in a vault when I am on the road - otherwise the whole content of the vault would be unencrypted available through docfetcher.

The workaround (read compromise) is to index the files outside of the vault and after indexing move the whole portable-docfetcher-directory into the vault. This means I have to update the indexes once every while. Still testing this scenario.