Confusion Over Three Parts in Typesense Cloud
TLDR AK asked for clarification about three parts in Typesense Cloud. Kishore Nallan explained what each part was.
Powered by Struct AI
1
1
3
16mo
Aug 28, 2022 (16 months ago)
AK
AK
09:55 AMWith what should these three parts be changed with? there is no enough and clear documentation that describes them well " if there are any please let me know "
Kishore Nallan
Kishore Nallan
09:57 AMIf you are using Typesense Cloud, then
host will be just the host name, e.g. <http://foo-1.a1.typesense.net|foo-1.a1.typesense.net> and port will be 443 and protocol will be https1
AK
AK
09:59 AMThanks Kishore Nallan
1
Typesense
Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Launch with HTTPS Protocol via Docker
Gines struggled to launch Typesense with HTTPS, initially failing to mount the certificate directory in Docker. Even after addressing this, Gines hit an SSL error, to which Kishore Nallan confirmed that an actual hostname, not an IP address, was needed.
8
15mo
Changing Typesense Server Bind Address
Zaiste wanted to bind Typesense server to `localhost` instead of the hostname. Jason guided on using API and peering address to change the binding IP.
4
26mo
Discussing Transition to TypeSense Cloud
Stephano indicated the transition to TypeSense Cloud from self-hosted solution. Jason offered to assist in configuring for the new setup.
2
34mo