PHPackages s2/rose - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Search & Filtering](/categories/search) 4. / 5. s2/rose ActiveLibrary[Search & Filtering](/categories/search) s2/rose ======= Search engine for PHP sites v3.0.0(1y ago)1225.9k—0%42MITPHPPHP >=7.4CI passing Since Jan 27Pushed 6mo ago12 watchersCompare [ Source](https://github.com/parpalak/rose)[ Packagist](https://packagist.org/packages/s2/rose)[ RSS](/packages/s2-rose/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (10)Dependencies (4)Versions (24)Used By (2) Rose ==== [](#rose) This is a search engine designed for content sites with simplified yet functional English and Russian morphology support. It indexes your content and provides a full-text search. [![](doc/rose.svg)](doc/rose.svg) Requirements ------------ [](#requirements) 1. PHP 7.4 or later. 2. A relational database in case of significant content size. Supported databases are: DatabaseTestsMySQL 5.6 or later and MariaDB 10.2 or later[![Tests on MySQL](https://github.com/parpalak/rose/actions/workflows/test_mysql.yml/badge.svg)](https://github.com/parpalak/rose/actions/workflows/test_mysql.yml)PostgreSQL (tested on versions 10...16)[![Tests on PostgreSQL](https://github.com/parpalak/rose/actions/workflows/test_postgres.yml/badge.svg)](https://github.com/parpalak/rose/actions/workflows/test_postgres.yml)SQLite (tested on 3.37.2)[![Tests on SQLite](https://github.com/parpalak/rose/actions/workflows/test_sqlite.yml/badge.svg)](https://github.com/parpalak/rose/actions/workflows/test_sqlite.yml)Installation ------------ [](#installation) ``` composer require s2/rose ``` Usage ----- [](#usage) ### Preparing Storage [](#preparing-storage) The index can be stored in a database or in a file. A storage serves as an abstraction layer that conceals implementation details. In most cases you need database storage `PdoStorage`. The storage is required for both indexing and searching. ``` $pdo = new \PDO('mysql:host=127.0.0.1;dbname=s2_rose_test;charset=utf8', 'username', 'passwd'); $pdo->setAttribute(\PDO::ATTR_ERRMODE, \PDO::ERRMODE_EXCEPTION); use S2\Rose\Storage\Database\PdoStorage; $storage = new PdoStorage($pdo, 'table_prefix_'); ``` When you want to rebuild the index, you call `PdoStorage::erase()` method: ``` $storage->erase(); ``` It drops index tables (if they exist) and creates new ones from scratch. This method is sufficient for upgrading to a new version of Rose that may not be backward compatible with the existing index. ### Morphology [](#morphology) For natural language processing, Rose uses stemmers. The stemmer truncates the inflected part of words, and Rose processes the resulting stems. Rose does not have built-in dictionaries, but it includes heuristic stemmers developed by Porter. You can integrate any other algorithm by implementing the StemmerInterface. ``` use S2\Rose\Stemmer\PorterStemmerEnglish; use S2\Rose\Stemmer\PorterStemmerRussian; // For optimization primary language goes first (in this case Russian) $stemmer = new PorterStemmerRussian(new PorterStemmerEnglish()); ``` ### Indexing [](#indexing) `Indexer` builds the search index. It depends on a stemmer and a storage. ``` use S2\Rose\Indexer; $indexer = new Indexer($storage, $stemmer); ``` Indexer accepts your data in a special format. The data must be wrapped in the `Indexable` class: ``` use S2\Rose\Entity\Indexable; // Main parameters $indexable = new Indexable( 'id_1', // External ID - an identifier in your system 'Test page title', // Title 'This is the first page to be indexed. I have to make up a content.', 1 // Instance ID - an optional ID of your subsystem ); // Other optional parameters $indexable ->setKeywords('singlekeyword, multiple keywords') // The same as Meta Keywords ->setDescription('Description can be used in snippets') // The same as Meta Description ->setDate(new \DateTime('2016-08-24 00:00:00')) ->setUrl('url1') ->setRelevanceRatio(3.14) // Multiplier for important pages ; $indexer->index($indexable); $indexable = new Indexable( 'id_2', 'Test page title 2', 'This is the second page to be indexed. Let\'s compose something new.' ); $indexable->setKeywords('content, page'); $indexer->index($indexable); ``` The constructor of `Indexable` has 4 arguments: - external ID - an arbitrary string that is sufficient for your code to identify the page; - page title; - page content; - instance ID - an optional integer ID of the page source (e.g., for multi-site services), as explained below. Optional parameters that you can provide include: keywords, description, date, relevance ratio, and URL. Keywords are indexed and searched with higher relevance. The description can be used for building a snippet (see below). It is suggested to use the content of "keyword" and "description" meta-tags, if available, for this purpose. The URL can be an arbitrary string. The `Indexer::index()` method is used for both adding and updating the index. If the content is unchanged, this method skips the operation. Otherwise, the content is being removed and indexed again. When you remove a page from the site, simply call ``` $indexer->removeById($externalId, $instanceId); ``` ### Searching [](#searching) Full-text search results can be obtained via `Finder` class. `$resultSet->getItems()` returns all the information about content items and their relevance. ``` use S2\Rose\Finder; use S2\Rose\Entity\Query; $finder = new Finder($storage, $stemmer); $resultSet = $finder->find(new Query('content')); foreach ($resultSet->getItems() as $item) { // first iteration: second iteration: $item->getId(); // 'id_2' 'id_1' $item->getInstanceId(); // null 1 $item->getTitle(); // 'Test page title 2' 'Test page title' $item->getUrl(); // '' 'url1' $item->getDescription(); // '' 'Description can be used in snippets' $item->getDate(); // null new \DateTime('2016-08-24 00:00:00') $item->getRelevance(); // 4.1610856664112195 0.26907154598642522 $item->getSnippet(); // 'This is the second page...' 'I have to make up a content.' } ``` Modify the `Query` object to use a pagination: ``` $query = new Query('content'); $query ->setLimit(10) // 10 results per page ->setOffset(20) // third page ; $resultSet = $finder->find($query); $resultSet->getTotalCount(); // Returns total amount of found items (for pagination links) ``` Provide instance id to limit the scope of the search with a subsystem: ``` $resultSet = $finder->find((new Query('content'))->setInstanceId(1)); foreach ($resultSet->getItems() as $item) { // first iteration only: $item->getId(); // 'id_1' $item->getInstanceId(); // 1 } ``` ### Highlighting and Snippets [](#highlighting-and-snippets) It's a common practice to highlight the found words in the search results. You can obtain the highlighted title: ``` $resultSet = $finder->find(new Query('title')); $resultSet->getItems()[0]->getHighlightedTitle($stemmer); // 'Test page title' ``` This method requires the stemmer since it takes into account the morphology and highlights all the word forms. By default, words are highlighted with italics. You can change the highlight template by calling `$finder->setHighlightTemplate('%s')`. Snippets are small text fragments containing found words that are displayed at a search results page. Rose processes the indexed content and selects best matching sentences. ``` use S2\Rose\Entity\ExternalContent; use S2\Rose\Snippet\SnippetBuilder; $finder->setSnippetLineSeparator(' · '); // Set snippet line separator. Default is '... '. $resultSet->getItems()[0]->getSnippet(); // 'I have to make up a content. · I have changed the content.' ``` Words in the snippets are highlighted the same way as in titles. If building snippets takes a lot of time, try to use pagination to reduce the number of snippets processed. ### Instances [](#instances) Instances can be helpful to restrict the scope of search. For example, you can try to index blog posts with `instance_id = 1` and comments with `instance_id = 2`. Then you can run queries with different restrictions: - `(new Query('content'))->setInstanceId(1)` searches through blog posts, - `(new Query('content'))->setInstanceId(2)` searches through comments, - `(new Query('content'))` searches everywhere. When indexing, if you omit instance\_id or provide `instance_id === null`, a value `0` will be used internally. Such content can only match queries without instance\_id restrictions. ### Content format and extraction [](#content-format-and-extraction) Rose is designed for the websites and web applications. It supports HTML format of the content by default. However, it is possible to extend the code to support other formats (e.g. plain text, markdown). This can be done by creating a custom extractor: ``` use S2\Rose\Extractor\ExtractorInterface; use S2\Rose\Indexer; class CustomExtractor implements ExtractorInterface { // ... // Please refer to the source code // to figure out how to create an extractor. } $indexer = new Indexer($storage, $stemmer, new CustomExtractor(), new Logger()); ``` ### Recommendations [](#recommendations) PdoStorage has the capability to identify similar items within the entire set of indexed items. Consider a scenario where you have a blog and its posts are indexed using Rose. This particular feature allows you to choose a set of other posts for each individual post, enabling visitors to explore related content. The data structure within the full-text index is well-suited for the task of selecting similar posts. To put it simply, regular search entails selecting relevant posts based on words from a search query, whereas post recommendations involve selecting other posts based on the words present in a given post. You can retrieve recommendations by invoking the following method: ``` $similarItems = $readStorage->getSimilar(new ExternalId('id_2')); // The result contains the following data: // $similarItems[0] = [ // 'tocWithMetadata' => new TocEntryWithMetadata(...), // 'external_id' => 'id_1', // 'instance_id' => '1', // 'title' => 'Test page title', // 'snippet' => 'This is the first page to be indexed.', // 'snippet2' => 'I have to make up a content.', // ], ``` Note Recommendations are supported on MySQL and PostgreSQL databases. They are not implemented in SQLite due to limited SQL support. ### Health Score 49 — FairBetter than 95% of packages Maintenance53 Moderate activity, may be stable Popularity35 Limited adoption so far Community21 Small or concentrated contributor base Maturity73 Established project with proven stability Bus Factor1 Top contributor holds 99% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~120 days Recently: every ~63 days Total 21 Last Release 632d ago Major Versions v0.4 → 1.02023-05-25 v1.1 → v2.02023-11-17 v2.1.0 → v3.0.02024-08-24 PHP version history (3 changes)v0.1.0PHP >=5.4.0 v0.3.2PHP >=5.6 1.0PHP >=7.4 ### Community Maintainers ![](https://www.gravatar.com/avatar/409ab88db05adaa27d7c408d7133fa5206486f24673718454e1d9e443a2e5ced?d=identicon)[s2](/maintainers/s2) --- Top Contributors [![parpalak](https://avatars.githubusercontent.com/u/9402484?v=4)](https://github.com/parpalak "parpalak (204 commits)")[![bolknote](https://avatars.githubusercontent.com/u/392509?v=4)](https://github.com/bolknote "bolknote (1 commits)")[![maximal](https://avatars.githubusercontent.com/u/980679?v=4)](https://github.com/maximal "maximal (1 commits)") --- Tags morphologyrelevancesearchsnippets ### Code Quality TestsCodeception ### Embed Badge ![Health badge](/badges/s2-rose/health.svg) ``` [![Health](https://phpackages.com/badges/s2-rose/health.svg)](https://phpackages.com/packages/s2-rose) ``` ### Alternatives [elasticsearch/elasticsearch PHP Client for Elasticsearch 5.3k178.3M943](/packages/elasticsearch-elasticsearch)[opensearch-project/opensearch-php PHP Client for OpenSearch 15224.3M65](/packages/opensearch-project-opensearch-php)[jeroen-g/explorer Next-gen Elasticsearch driver for Laravel Scout. 397612.3k](/packages/jeroen-g-explorer)[loupe/loupe A full text search engine with tokenization, stemming, typo tolerance, filters and geo support based on only PHP and SQLite 497185.2k14](/packages/loupe-loupe)[manticoresoftware/manticoresearch-php PHP Client for Manticore Search 206550.0k16](/packages/manticoresoftware-manticoresearch-php)[terminal42/escargot A web crawler or spider library based on Symfony components 581.4M3](/packages/terminal42-escargot) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)