![\"Meiliserach](\"https:\/\/4eck-media.de\/wp-content\/uploads\/2025\/11\/meilisearch_mainpage_fbc63e3ac0.avif\" "\\"\\"")
\n<\/picture>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/section>We ultimately chose the open-source version of Meilisearch. This version was selected because it gave us complete control over the search results, without additional costs for licensing fees or external developers, where it is not even certain if they would be able to manage the project, as we have unfortunately experienced in the past. <\/p>
The implementation of Meilisearch<\/h2>
The integration of Meilisearch into our platform TutKit.com was the first step towards improving the search functionality. Here are the details of how we implemented Meilisearch and how it is currently managed in our company. <\/p>
Setup and configuration<\/h3>
We decided to use Meilisearch in its open-source version to maintain complete control over our search solutions. The installation began by downloading the Meilisearch server from the official website. To ensure stable and reliable operation, we set up a systemd service. This service was configured to automatically start Meilisearch as soon as the server boots up and to automatically restart the service in case of a failure. <\/p>
# Beispiel für eine systemd-Dienstdatei für Meilisearch\n[Unit]\nDescription=MeiliSearch\nAfter=systemd-user-sessions.service\n\n[Service]\nType=simple\nExecStart=\/usr\/bin\/meilisearch --http-addr 127.0.0.1:7700 --env production --master-key *****\nRestart=on-failure\nRestartSec=5s\n\n[Install]\nWantedBy=multi-user.target\n<\/code><\/pre>Security configuration<\/h3>
Security is an important aspect when configuring Meilisearch. We have created two keys to meet the security requirements. The master key, which allows full access to the Meilisearch instance, is used exclusively in the backend. The API key, on the other hand, which has more limited permissions, is used for search operations and other user tasks. This separation ensures that critical backend operations are securely protected while interactions in the frontend remain efficient and secure. <\/p>
Integration with Laravel<\/h3>
Our platform TutKit.com is built on the PHP framework Laravel, and we have used the MeiliSearch-PHP library as the basis for the integration. The API key is used in our Laravel application to connect to Meilisearch. This significantly increases security, as only the functions allowed by the API key are accessible, minimizing the risk of unauthorized actions. <\/p>
\/\/ Beispiel für die Konfiguration von Meilisearch in Laravel\n'connections' => [\n 'meilisearch' => [\n 'host' => env('MEILISEARCH_HOST', 'http:\/\/localhost:7700'),\n 'key' => env('MEILISEARCH_KEY', null),\n ],\n],\n<\/code><\/pre>Indexing and Data Management <\/h3>
A central aspect of our implementation was the efficient management and indexing of data. We developed a custom console command in Laravel that is specifically designed for extensive updates or for initiating the indexing process. This command specifically targets only the relevant records that need to be indexed. This allows us to avoid unnecessary data processing and focus on the essential information. <\/p>
\/\/ Beispiel für einen benutzerdefinierten Konsolenbefehl in Laravel\nArtisan::command('index:content', function () {\n \/\/ Code zur Indexierung der relevanten Datensätze\n})->describe('Indexiere alle relevanten Inhalte');\n<\/code><\/pre>The example is, of course, very simple. Our command code has 400 lines. <\/p>
Automatic update of indices in the search.<\/h3>
A key advantage of our implementation is the ability to automatically detect and respond to changes in Laravel models. Whenever data is updated, added, or deleted, the corresponding MeiliSearch index is promptly and efficiently updated to reflect only those changes. This targeted indexing approach eliminates the need for a full reindexing of all data and ensures that our MeiliSearch data remains up to date. Here is a code example when a blog post has been updated: <\/p>
if($this->status == 'PUBLIC') {\n $post_filtered = $this->prepareSearchField();\n $searchClient->index('suggestions')->updateDocuments([\n [\n 'id' => 'blog_post_lang_'.$this->id,\n 'language' => $this->language->code,\n 'suggestion' => SearchHelper::prepareSearchSuggestion($this->title),\n 'indexation_type' => 'suggestion',\n 'type' => 'blog_post',\n ]\n ]);\n\n $searchClient->index('blog_posts')->updateDocuments([$post_filtered]);\n } else {\n $searchClient->index('blog_posts')->deleteDocument($this->id);\n $searchClient->index('suggestions')->deleteDocument('blog_post_lang_'.$this->id);\n }\n<\/code><\/pre>This code example is also extremely simple, and our lines of code operate on different models and different statuses. But in principle, it is clear what it’s about. <\/p>
Optimization and Maintenance<\/h3>
Regular maintenance and optimization of the Meilisearch integration is crucial for long-term performance. By utilizing the regular updates from Meilisearch, we benefit from continuous improvements and new features. This ensures that our search solution remains up-to-date and can keep pace with the growing demands of our platform. <\/p>
![\"Meilisearch](\"https:\/\/4eck-media.de\/wp-content\/uploads\/2025\/11\/Meilisearch_f5b0c6bff5.avif\" "\\"\\"")
\n<\/picture>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/section>