Thinking Sphinx is a library for connecting ActiveRecord to the Sphinx full-text search tool, and integrates closely with Rails (but also works with other Ruby web frameworks). The current release is v3.1.0.
Please refer to the release notes for any changes you need to make when upgrading:
If you’re upgrading from pre-v3, then the documentation has pretty extensive notes on what’s changed.
It’s a gem, so install it like you would any other gem. You will also need to specify the mysql2 gem if you’re using MRI, or jdbc-mysql if you’re using JRuby:
gem 'mysql2', '0.3.13', :platform => :ruby gem 'jdbc-mysql', '5.1.28', :platform => :jruby gem 'thinking-sphinx', '3.1.0'
The MySQL gems mentioned are required for connecting to Sphinx, so please include it even when you’re using PostgreSQL for your database.
You’ll also need to install Sphinx – this is covered in the extended documentation.
These are covered in a blog post.
Thinking Sphinx v3 is currently built for Sphinx 2.0.5 or newer, and releases since v3.1.0 expect Sphinx 2.1.2 or newer by default.
Currently Thinking Sphinx 3 is built to support Rails/ActiveRecord 3.2 or newer. If you’re using Sinatra and ActiveRecord instead of Rails, that’s fine – just make sure you add the
:require => 'thinking_sphinx/sinatra' option when listing
thinking-sphinx in your Gemfile.
If you want ActiveRecord 3.1 support, then refer to the 3.0.x releases of Thinking Sphinx. Anything older than that, then you’re stuck with Thinking Sphinx v2.x (for Rails/ActiveRecord 3.0) or v1.x (Rails 2.3). Please note that these older versions are no longer actively supported.
You’ll need either the standard Ruby (v1.9.3 or newer) or JRuby. I’m open to patches to improve Rubinius support (if required – it may work with it right now).
JRuby is only supported as of Thinking Sphinx v3.1.0, and requires Sphinx 2.1.2 or newer.
MySQL 5.x and Postgres 8.4 or better are supported.
To contribute, clone this repository and have a good look through the specs – you’ll notice the distinction between acceptance tests that actually use Sphinx and go through the full stack, and unit tests (everything else) which use liberal test doubles to ensure they’re only testing the behaviour of the class in question. I’ve found this leads to far better code design.
All development is done on the
develop branch; please base any pull requests off of that branch. Please write the tests and then the code to get them passing, and send through a pull request.
In order to run the tests, you’ll need to create a database named
# Either fire up a MySQL console: mysql -u root # OR a PostgreSQL console: psql # In that console, create the database: CREATE DATABASE thinking_sphinx;
You can then run the unit tests with
rake spec:unit, the acceptance tests with
rake spec:acceptance, or all of the tests with just
rake. To run these with PostgreSQL, you’ll need to set the `DATABASE` environment variable accordingly:
Copyright © 2007-2014, Thinking Sphinx is developed and maintained by Pat Allan, and is released under the open MIT Licence. Many thanks to all who have contributed patches.