# Meilisearch ### Running Meilisearch locally Since Meilisearch is open source, you can run it locally or setup your own hosted version for production. If you use DDEV you can use the add-on from Kevin Quillen. It is very easy to setup. We can't provide support for this, but this is what worked for us. ``` ddev add-on get kevinquillen/ddev-meilisearch ``` Once installed update your `meilisearch` config setting to look like this: ```php 'meilisearch' => [ 'url' => 'http://meilisearch:7700', 'appKey' => 'ddev', ], ``` And the GUI will be accessible at `https://your-project.ddev.site:7701` . The main downside to running Meilisearch locally and using the GUI is that you do not have a robust point and click interface to configure your indexes. You will need to create a .json config file, then use the Dexter control panel page to import it into Meilisearch. The hosted version of Meilisearch is more intuitive and friendly for new users. You can use this basic configuration file to get started. Refer to the Meilisearch docs for more information. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.boldminded.com/dexter/docs-craft/meilisearch.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.