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.
Aug 28, 2022 (16 months ago)
Kishore Nallan09:57 AM
hostwill be just the host name, e.g.
<http://foo-1.a1.typesense.net|foo-1.a1.typesense.net>and port will be
443and protocol will be
Indexed 3015 threads (79% resolved)
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.
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.
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.