4 ms·
I put together an autocomplete service using Ruby and Redis but rather than dealing with the network latency of a remote service I decided to package it up so i
by doomspork 12y ago
I put together an autocomplete service using Ruby and Redis but rather than dealing with the network latency of a remote service I decided to package it up so it could be mounted along side my app: https://github.com/doomspork/autocomplete-me https://github.com/doomspork/autocomplete-me
- mosburger 12y agoYeah, where I work we use another redis + ruby gem that the seatgeek guys wrote called soulmate. https://github.com/seatgeek/soulmate https://github.com/seatgeek/soulmate
- peterbe 12y agoCool! It seems a bit more flexible but it requires jQuery and the plugin itself is 11Kb.
- doomspork 12y agoThe inclusion of a JS library is only a convenience. There more robust solutions for the UI like Twitter's Typeahead.js https://github.com/twitter/typeahead.js https://github.com/twitter/typeahead.js
- doomspork 12y agoThis is awesome, I hadn't seen it before. Thanks for sharing!
- ericwaller 12y agoHeh, I always feel a bit bad when people mention this since we're not using it ourselves anymore. Though it's a nice and easy way to get going quickly if you're already running redis (and especially if you've got a rails app). We're using elasticsearch now which is definitely a bit more of an operational headache.
- peterbe 12y agoSo, it loads all titles into the client?
- doomspork 12y agoSorry I'm not sure I follow. There is no client included within my repo, just the service.