- Issue created by @hktang
Meilisearch search engine is much simpler than Solr, so it doesn't have a similar concept of cores from Solr.
Meilisearch configurations are usually per the meilisearch server. So you'd have to start a new meilisearch server for each environment, especially if you have clashing index names.
If you want to migrate data from one server to another, you can use snapshots or dumps in this case dumps are probably the better choice. But this doesn't only create a copy of settings but also indexes and documents in those indexes.
But as I said, Meilisearch is purposefully made to be simple, so it can be easy & quick to set up and use.
Now how to correctly handle between different deployments of a website. Well for the most part you can export Drupal configs and import them and then by hand just replace the Server URL and Master Key, after doing that, the backend configures Meilisearch.
- Status changed to Closed: works as designed
12 months ago 9:54pm 26 November 2023 - 🇸🇮Slovenia bcizej
I think @admirlju explained everything, Meilisearch does not have a concept of cores like Solr so I am closing this issue.
- 🇯🇵Japan hktang
Sure! Thanks for your reply.
As an update, and for anyone who's having similar requirements, I ended up using Docker to spin up difference instances for this purpose.
Official docker images are available at https://hub.docker.com/r/getmeili/meilisearch/tags