You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reported this issue typesense/firestore-typesense-search#60 and I thought, it's a Firebase plugin issue, turns out the javascript library accepts only one key for all nodes which makes no sense, is this by design?
All Typesense libraries support one key per cluster, why?
Is it because you only set up a cluster using private IPs and you never thought that someone like me would want to set up servers in multiple data centers? So if a cluster is accessible privately only it's secure by design, this is the main reason, right?
The text was updated successfully, but these errors were encountered:
elieobeid7
changed the title
Add support for mulltiple API keys
Add support for mulltiple API keys per cluster
Oct 8, 2023
To use multiple API keys, you'd simply instantiate multiple instances of the client each with a separate API key... and use the appropriate client instance to call the methods needed.
We both know this isn't ideal, closing this ticket as it seems to me, this won't be fixed. I added one key for all servers and called it a day since I refuse to write such code.
I reported this issue typesense/firestore-typesense-search#60 and I thought, it's a Firebase plugin issue, turns out the javascript library accepts only one key for all nodes which makes no sense, is this by design?
All Typesense libraries support one key per cluster, why?
Is it because you only set up a cluster using private IPs and you never thought that someone like me would want to set up servers in multiple data centers? So if a cluster is accessible privately only it's secure by design, this is the main reason, right?
The text was updated successfully, but these errors were encountered: