Setup Searchkick Gem With Elasticsearch | Ruby On Rails 7 Tutorial
Вставка
- Опубліковано 30 вер 2024
- Setup search using Searchkick, Turbo, and Eleasticsearch. This allows for a powerful search solution with incredibly flexibility in Rails.
Checkout my course(s) at: learn.deanin.com
Today we add Searchkick and Elasticsearch to a project, implement a search bar and use turbo for no-refresh searching and indexing.
Gist Commands: gist.github.co...
Links:
github.com/ank...
www.digitaloce...
learn.microsof...
magento.stacke...
Join this channel to help support these videos:
/ @deanin
Follow me on social media:
linktr.ee/deanin
If you liked this video, please consider subscribing: t.co/RZ4EwP0F2a
#Deanin #Software #Programming
Great! Thanks!
PS Install elasticsearch on Mac OS:
brew tap elastic/tap
brew install elastic/tap/elasticsearch-full
brew services start elastic/tap/elasticsearch-full
Second, in GemFile change:
gem "elasticsearch", "< 7.14"
# gem "elasticsearch", "~> 8.5" # not worked on Ventura and elasticsearch > 7.14
Thank you! Pinning this for the Mac users. 🙂
This setup process was kind of annoying so I decided to make a video covering it. Hope it helps!
PS: Video is still processing so it might be blurry until UA-cam gives us a 1080p version. Sorry about that!
Hi ! We using opensearch in production, it was helpfull for me!
Can I ask one dumb question? What happens now to the index view now that you've taken the @ out of @posts ?
Can you search the whole site and not just the Posts? Thanks
Dean, I don't know how may times your channel has cleared up confusions and questions as a new Rails dev. Thank you.
Glad to hear it! As funny as it sounds, it's also how I've cleared up a lot of these questions for myself haha.
I've been learning so much with you, thank you.
Hi Dean, thank you for sharing the tutorial. When I tried to run Post.reindex, I got this error: The client is unable to verify that the server is Elasticsearch. Some functionality may not be compatible if the server is running an unsupported product.
First time I've seen this. From what I can tell it looks like a version issue, but that's about all I could find 🙃
I'll look into this more when I get home, sorry about that
I literally wanted to ask about this under your last video, nice!
Also, note to people using Opensearch, it might be worth adding
plugins.security.disabled: true
To your opensearch.yml if you run into any connection problems related to unsafe connection(if you're just running your local stuff without https), basically what was said in the video but for Opensearch.
Super helpful, thanks Dean.
useful video : )
If someone catch the error - "Unathorized" or "Faraday Error" create some file below "initializers" folder with this content:
Searchkick.client_options = {
url: 'localhost:9200',
retry_on_failure: true,
user: "admin",
password: "admin",
transport_options:
{
request: { timeout: 250 },
ssl: { verify: false }
}
}
I had a problem after starting the service on wsl2 on windows 10 which prevented me from accessing the service from windows browser when hitting localhost:9200, turns out instead of 'localhost' at 3:10 i used '_local_' and it worked
Thank you sooooo mutch! You saved my sanity