pg_search
turbo-rails
pg_search | turbo-rails | |
---|---|---|
7 | 48 | |
1,230 | 1,983 | |
0.6% | 1.4% | |
5.6 | 8.3 | |
6 days ago | 4 days ago | |
Ruby | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pg_search
-
The Ultimate Search for Rails - Episode 1
On the backend, we'll need a few tools. Apart from the classics (ActiveRecord scopes and the pg_search gem), you’ll see how the (yet officially unreleased but production-tested) all_futures gem, built by SR authors, will act as an ideal ephemeral object to temporarily store our filter params and host our search logic. Finally, we’ll use pagy for pagination duties.
-
Application Search Feature more that ActiveRecord;
You can take a look at pg_search if you’re using Postgres
-
How to build a search engine with Ruby on Rails
This was a really good read, thanks. I've got into the habit of jumping straight to PgSearch but could definitely apply this approach to some existing projects.
-
Instant search with Rails 6 and Hotwire
Cleaner, more performant database queries: Definitely don't just leave your query sitting in the controller! For production use cases, you'd want to consider an option like pg_search
-
Postgres Full-Text Search: A Search Engine in a Database
If you are using Rails with Postgres you can use pg_search gem to build the named scopes to take advantage of full text search.
https://github.com/Casecommons/pg_search
-
Tips for optimizing pg_search?
Hey guys. Looking to release an app for mobile that will be using a rails API. The app will heavily rely on search. I know the go-to is to use elasticsearch but wanted to see if there was enough user demand for the MVP before shelling out $50/mo for the heroku add on. In the mean time I've been using pg_search. From the eye test it's performing okay but will be adding a table that houses over 350K records. With this in mind I was wondering if you all had any tips for increasing the overall speed for search from the model and controller level. Also should note that I'm open to any other free search gems if they deem bette fit.
-
Rails Search Bar
There are two basic search configurations with pg_search, a Single Model search scope or a multi Model configuration. In my case I am only using the Single Model configuration, but you can read more about multi-search in the documentation.
turbo-rails
-
Can't get Rails 7 turbo_stream_from to update view from broadcast
The install notes here link to an issue specific to webpacker. Try that and see if it works?
-
Strong reasons to pick htmx, over hotwire?
True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.
-
Rails 7 - Turbo Frame and Turbo Stream
Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb
-
Use turbo_streams to update the client in real time from inside a loop?
So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.
-
Where do I start for learning "HTML over the wire"
Use this too: https://github.com/hotwired/turbo-rails
-
Using ViewComponents with Turbo
Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433
- is turbo and stimulus compatible with rails 4 ?
-
Turbo-Rails just got better
Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0
-
Live Visit Count for website or page. ActionCable, Turbo Broadcasts, Kredis
turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.
-
We're breaking up with JavaScript front ends
The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails
What are some alternatives?
ransack - Object-based searching.
Stimulus - A modest JavaScript framework for the HTML you already have
Elasticsearch Rails - Elasticsearch integrations for ActiveModel/Record and Ruby on Rails
hotwire-rails - Use Hotwire in your Ruby on Rails app
textacular - Textacular exposes full text search capabilities from PostgreSQL, and allows you to declare full text indexes. Textacular will extend ActiveRecord with named_scope methods making searching easy and fun!
Turbolinks - Turbolinks makes navigating your web application faster
elasticsearch-ruby - Ruby integrations for Elasticsearch
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
Searchkick - Intelligent search made easy
hotwire-tabs
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.