Algolia and Laravel Scout
Introducing Laravel Scout
With the addition of Laravel Scout, Laravel has provided an easy interface into Algolia’s API Client, greatly simplifying your use of Algolia within the framework.
Though Scout is designed to work with any engine, it was actually built with Algolia in mind. At the time of this writing, Algolia is the only search engine that Laravel officially supports.
For these reasons, we encourage you to start using Scout for all of your Algolia data indexing and synchronization. As for building UIs, we discuss your options below.
If you want see some code, we built an example project showcasing some of the feature of Algolia and Laravel Scout: https://github.com/algolia/algoliasearch-laravel-example
Laravel has written excellent online documentation to go along with its release of Scout. They go into great detail on how to use the Scout interface. Additionally, there are Laracasts that can help you get started with Scout and Algolia. These resources should be sufficient not only to help you get started, but to implement Algolia in the best possible way within the Laravel framework.
One of our goals here is to complement Laravel’s documentation by anticipating questions you might have after reading Laravel’s documentation. We touch on some of the same material, adding our point of view to such subjects as installation, managing indices, and others.
Of equal interest, we show you how to extend Scout with callbacks and extended devices, and how to use the Macros we have written to simplify your code. We also provide tutorials that showcase special use cases, like geo-awareness.
The client side of Laravel
Looking for the legacy package?
Before Scout came out, we had built our own Laravel integration. However, given the benefits of Scout, and its compatibility with Algolia, we really encourage you to switch over to Scout.
If you are still using our previous package, you can access its documentation here in the Readme of the package.
Did you find this page helpful?
We're always looking for advice to help improve our documentation!
Please let us know what's working (or what's not!).
We're constantly iterating thanks to the feedback we receive.