I’m going to give Typesense a try today. I’m just working on a Rails app and went from Meilisearch (which is great) to Elastic for some more complex aggregation queries but this seems like a good option for instant search like behavior too.

Glad to see the Avo project live and well!

I previously used Opensearch for my Rails project, it was quite heavy piece of service to run in the docker compose environment. I said to my myself that on the next project, I will eitber use Typesense or Meilisearch. I'll bookmark this guide for when the time comes

Regarding the command to create the Rails app, I would have done this for the playground project

rails new typesense -d sqlite3 -c tailwind -j esbuild --skip-test --skip-jbuilder --skip-action-mailbox --skip-action-text

I love Jason Bosco (the typesense guy). I love Ruby on Rails. But I've been using Meilisearch more and more over the past year on client projects. They maintain a top of the line Rails integration: https://github.com/meilisearch/meilisearch-rails

I’m debating Typesense vs. Meilisearch for a project. My use case isn’t particularly complex so either fits.

Curious if anyone has any horror stories about either

  yet again I reached for a dependency when Postgres is enough

Typesense also maintains a native Rails integration (fork of Algolia's one). You can automatically index on write, conditionally index documents based on business logic and a bunch more.

https://github.com/typesense/typesense-rails