Convert Figma logo to code with AI

teamtnt logolaravel-scout-tntsearch-driver

Driver for Laravel Scout search package based on https://github.com/teamtnt/tntsearch

1,091
142
1,091
15

Top Related Projects

1,539

Laravel Scout provides a driver based solution to searching your Eloquent models.

This package offers advanced functionality for searching and filtering data in Elasticsearch.

Quick Overview

The teamtnt/laravel-scout-tntsearch-driver is a package that provides a TNTSearch driver for the Laravel Scout search abstraction layer. It allows you to easily integrate the powerful TNTSearch full-text search engine into your Laravel applications.

Pros

  • Seamless Integration with Laravel Scout: The package integrates seamlessly with the Laravel Scout API, making it easy to set up and use within your Laravel projects.
  • Powerful Full-Text Search: TNTSearch is a highly performant and feature-rich full-text search engine, providing advanced search capabilities.
  • Flexible Configuration: The package offers various configuration options, allowing you to customize the search behavior to fit your specific needs.
  • Actively Maintained: The project is actively maintained by the TeamTNT organization, ensuring regular updates and bug fixes.

Cons

  • Limited Documentation: The project's documentation could be more comprehensive, making it challenging for new users to get started.
  • Dependency on TNTSearch: The package is dependent on the TNTSearch library, which may not be as widely used as other search solutions like Elasticsearch or Algolia.
  • Potential Performance Concerns: Depending on the size and complexity of your data, the TNTSearch engine may not perform as well as other more scalable search solutions.
  • Lack of Community Support: Compared to more popular search solutions, the package may have a smaller community and fewer resources available for troubleshooting and support.

Code Examples

Here are a few code examples demonstrating the usage of the teamtnt/laravel-scout-tntsearch-driver package:

  1. Configuring the TNTSearch Driver:
// config/scout.php
return [
    'driver' => 'tntsearch',
    'tntsearch' => [
        'storage'  => storage_path(), // where the index files will be stored
        'fuzziness' => env('TNTSEARCH_FUZZINESS', false),
        'fuzzy' => [
            'prefix_length' => 2,
            'max_expansions' => 50,
            'distance' => 2
        ],
        'asYouType' => false,
        'searchBoolean' => false,
    ],
];
  1. Indexing a Model:
use TeamTNT\Scout\Engines\TNTSearchEngine;

class Product extends Model
{
    use Searchable;

    public function searchableAs()
    {
        return 'products_index';
    }

    public function toSearchableArray()
    {
        return [
            'id' => $this->id,
            'name' => $this->name,
            'description' => $this->description,
        ];
    }
}
  1. Performing a Search:
$products = Product::search('search term')->get();
  1. Customizing the Search Query:
$products = Product::search('search term')
    ->where('category', 'electronics')
    ->orderBy('price', 'desc')
    ->get();

Getting Started

To get started with the teamtnt/laravel-scout-tntsearch-driver package, follow these steps:

  1. Install the package using Composer:
composer require teamtnt/laravel-scout-tntsearch-driver
  1. Publish the package's configuration file:
php artisan vendor:publish --provider="TeamTNT\Scout\TNTSearchScoutServiceProvider"
  1. Configure the TNTSearch driver in your config/scout.php file:
'driver' => 'tntsearch',
'tntsearch' => [
    'storage'  => storage_path(), // where the index files will be stored
    'fuzziness' => env('TNTSEARCH_FUZZINESS', false),
    'fuzzy' => [
        'prefix_length' => 2,
        'max_expansions' => 50,
        'distance' => 2
    ],
    'asYouType' => false,
    'searchBoolean' => false,
]

Competitor Comparisons

1,539

Laravel Scout provides a driver based solution to searching your Eloquent models.

Pros of Laravel Scout

  • Abstraction: Laravel Scout provides a simple, fluent API for adding full-text search to Eloquent models, abstracting away the underlying search engine implementation.
  • Flexibility: Scout supports multiple search engine drivers, including Algolia, Meilisearch, and Elasticsearch, allowing developers to choose the best fit for their project.
  • Ease of Use: Scout's integration with Laravel's Eloquent makes it easy to set up and use, with minimal configuration required.

Cons of Laravel Scout

  • Limited Customization: While Scout supports multiple drivers, the level of customization available for each driver may be limited compared to using the driver directly.
  • Performance: Depending on the size of the dataset and the complexity of the search queries, Scout's performance may not be as optimal as using the search engine driver directly.

Code Comparison

Laravel Scout:

use Laravel\Scout\Searchable;

class Post extends Model
{
    use Searchable;

    public function toSearchableArray()
    {
        return $this->toArray();
    }
}

teamtnt/laravel-scout-tntsearch-driver:

use TeamTNT\Scout\Engines\TNTSearchEngine;

class Post extends Model
{
    use Searchable;

    public function searchableAs()
    {
        return 'posts_index';
    }
}

This package offers advanced functionality for searching and filtering data in Elasticsearch.

Pros of Scout Elasticsearch Driver

  • Supports Elasticsearch versions 6.x and 7.x, providing flexibility in choosing the appropriate version for your project.
  • Offers advanced search features like fuzzy matching, proximity search, and more, which can be useful for complex search requirements.
  • Provides a well-documented and easy-to-use API, making it straightforward to integrate with your Laravel application.

Cons of Scout Elasticsearch Driver

  • Requires an Elasticsearch cluster to be set up and maintained, which can add complexity to the deployment process.
  • May have a higher learning curve compared to the TNT Search driver, as it requires understanding Elasticsearch concepts and configurations.
  • Can be more resource-intensive than the TNT Search driver, especially for large datasets, due to the overhead of the Elasticsearch cluster.

Code Comparison

Scout Elasticsearch Driver:

$results = Scout::search('query')->paginate(10);

Laravel Scout TNT Search Driver:

$results = Scout::search('query')->paginate(10);

The code for both drivers is very similar, as they both leverage the Laravel Scout API. The main difference lies in the underlying search engine used (Elasticsearch vs. TNT Search).

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

TNTSearch Driver for Laravel Scout - Laravel 5.3 - 11

Backers on Open Collective Sponsors on Open Collective Latest Version on Packagist Software License Build Status Quality Score Total Downloads

This package makes it easy to add full text search support to your models with Laravel 5.3 to 9.0.

Premium products

If you find TNT Search to be one of your valuable assets, take a look at one of our premium products

Support us on Open Collective

Contents

Installation

You can install the package via composer:

composer require teamtnt/laravel-scout-tntsearch-driver

Add the service provider:

// config/app.php
'providers' => [
    // ...
    TeamTNT\Scout\TNTSearchScoutServiceProvider::class,
],

Ensure you have Laravel Scout as a provider too otherwise you will get an "unresolvable dependency" error

// config/app.php
'providers' => [
    // ...
    Laravel\Scout\ScoutServiceProvider::class,
],

Add SCOUT_DRIVER=tntsearch to your .env file

Then you should publish scout.php configuration file to your config directory

php artisan vendor:publish --provider="Laravel\Scout\ScoutServiceProvider"

In your config/scout.php add:


'tntsearch' => [
    'storage'  => storage_path(), //place where the index files will be stored
    'fuzziness' => env('TNTSEARCH_FUZZINESS', false),
    'fuzzy' => [
        'prefix_length' => 2,
        'max_expansions' => 50,
        'distance' => 2,
	'no_limit' => true
    ],
    'asYouType' => false,
    'searchBoolean' => env('TNTSEARCH_BOOLEAN', false),
    'maxDocs' => env('TNTSEARCH_MAX_DOCS', 500),
],

To prevent your search indexes being commited to your project repository, add the following line to your .gitignore file.

/storage/*.index

The asYouType option can be set per model basis, see the example below.

Usage

After you have installed scout and the TNTSearch driver, you need to add the Searchable trait to your models that you want to make searchable. Additionaly, define the fields you want to make searchable by defining the toSearchableArray method on the model:

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;
use Laravel\Scout\Searchable;

class Post extends Model
{
    use Searchable;

    public $asYouType = true;

    /**
     * Get the indexable data array for the model.
     *
     * @return array
     */
    public function toSearchableArray()
    {
        $array = $this->toArray();

        // Customize array...

        return $array;
    }
}

Then, sync the data with the search service like:

php artisan scout:import App\\Post

If you have a lot of records and want to speed it up you can run (note that with this you can no longer use model-relations in your toSearchableArray()):

php artisan tntsearch:import App\\Post

After that you can search your models with:

Post::search('Bugs Bunny')->get();

Scout status

php artisan scout:status

With this simple command you'll get a quick overview of your search indices.

Image of Scout Status Command

Or you can pass a searchable model argument:

php artisan scout:status "App\Models\Post"

If your models are not in the default location app or one of its subdirectories, you may set the modelPath option

// config/scout.php
'tntsearch' => [
    // ...
    'modelPath' => 'models',
],

Image of Scout Status Command

Constraints

Additionally to where() statements as conditions, you're able to use Eloquent queries to constrain your search. This allows you to take relationships into account.

If you make use of this, the search command has to be called after all queries have been defined in your controller.

The where() statements you already know can be applied everywhere.

namespace App\Http\Controllers;

use App\Post;

class PostController extends Controller
{
    /**
     * Display a listing of the resource.
     *
     * @return \Illuminate\Http\Response
     */
    public function index(Request $request)
    {
        $post = new Post;

        // filter out posts to which the given topic is assigned
        if($request->topic) {
            $post = $post->whereNotIn('id', function($query){
                $query->select('assigned_to')->from('comments')->where('topic','=', request()->input('topic'));
            });
        }

        // only posts from people that are no moderators
        $post = $post->byRole('moderator','!=');

        // when user is not admin filter out internal posts
        if(!auth()->user()->hasRole('admin'))
        {
            $post= $post->where('internal_post', false);
        }

        if ($request->searchTerm) {
            $constraints = $post; // not necessary but for better readability
            $post = Post::search($request->searchTerm)->constrain($constraints);
        }

        $post->where('deleted', false);

        $post->orderBy('updated_at', 'asc');

        $paginator = $post->paginate(10);
        $posts = $paginator->getCollection();

        // return posts
    }
}

Adding via Query

The searchable() method will chunk the results of the query and add the records to your search index.

$post = Post::find(1);

// You may also add record via collection...
$post->searchable();

// OR

$posts = Post::where('year', '>', '2018')->get();

// You may also add records via collections...
$posts->searchable();

When using constraints apply it after the constraints are added to the query, as seen in the above example.

OrderBy

An orderBy() statement can now be applied to the search query similar to the where() statement.

When using constraints apply it after the constraints are added to the query, as seen in the above example.

Sponsors

Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor]

Credits

Contributors

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers! 🙏 [Become a backer]