How to build a recoll search service across multiple AppVMs

User Support General
1

Hi, I would like to build a service that queries other AppVMs and gather some information.

It’s something like a search engine, but running on all qubes, if the ‘search’ option is enabled.

The search option can be implemented as something like the service tab in qubes settings. If a qube is search-enabled, then the indexing agent runs in the qube.

By default, the home directory gets indexed. But it might be customized per taste in the user’s local config.

I would prefer a xapiandb based indexer, such as recollindex, to get invoked in each qube where ‘search’ is enabled.

And have a search VM that runs the recoll console, which can read from qube indexes.

I would like to implement a simple solution like this, to make life easier when searching for documents. Currently, I start each qube and run recoll in it. I don’t like full scans in each qube, because it takes too long, whereas recoll is lightning-fast.

Are there any recent docs to read and/or follow, to build this kind of interaction?

2 Likes
2

If you have order in your qubes then you don’t need that, because all documents you have in 2 networkless qubes, vault and personal and eventually in one networked qube developing.
Then no need for inter qubes search engine.

1 Like
3

I understand your point, but in my case I have organized the qubes per project. I have many projects that are isolated, and I like it this way of doing work to avoid any cross-contamination or unwanted dependencies. That said, I have 20+ work AppVMs so far, some were archived.

1 Like