It seems this module requires its own standalone Typesense cluster. I cannot use this module with a Typesense cluster that is shared by other unrelated sites.
Is it possible to use this module with a Typesense cluster that is shared by other unrelated sites? For example, can I provide this module with a Typesense API key that is limited to specific Typesense collections, such as only those collections that match "acme_.*"?
I understand this would limit/restrict some UI features of this module from working. Is this a possibility? Or is this simply not the intended use-case for this module?
Active
1.0
Code
At the moment, you cannot use the module to point to an existing collection (because the collection is created by Drupal with the information you set in the schema tab).
If a collection with that name doesn't exist on the cluster, I don't see any problem using the module. What issues have you found?
To restrict access, you can create an API key that allows access to only some collections and use that key on the server configuration page.