Typesense port protocol params #38
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Bermudez0622 The reason we haven't allowed protocol to be configured in the extension is because the trigger functions run on Firebase and so we don't want calls to Typesense going over an unencrypted http connection via the public internet, to any Typesense Cluster, self-hosted or not... Are you able to setup an SSL cert on your self-hosted Typesense node and use the default 443/https. LetsEncrypt for example has free SSL certs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
If Typesense self hosted cluster is not running at 443 port, firestore will not sync changes
PR Checklist