Deploying Typesense on Heroku Troubleshooting
TLDR VIVEK encountered an error while deploying Typesense on Heroku. Jason advised that Typesense might not be suitable for Heroku, and suggested increasing node capacity to solve the specific error.
Jul 20, 2022 (17 months ago)
Although, does Heroku give you access to persistent disk and also do they let containers run without interruption? If no, then Typesense will not be suitable, because it needs both of these given that it’s an in-memory datastore, with a backup on disk.
Indexed 3015 threads (79% resolved)
Deploying Typesense on Google Cloud Run
Nicolas attempted to deploy Typesense on Google Cloud Run but encountered problems. CaptainCodeman advised that Cloud Run is unsuitable for Typesense and suggested using a container optimized VM.
Discussion on Deploying Typesense on Render.com
Matthias shared their deployment template for Typesense on Render.com which led to a discussion with Jason about docker volumes and memory allocation. Janaka made a point on private deployment.
Troubleshooting Typesense Document Import Error
Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.