Please add the version number of meiliadmin to the dashboard.

I'd like to run this script in my Symfony project, and trying to think of the best way to do it.

I'm wondering if this workflow would be appropriate:

composer install survos/meiliadmin-bundle

Add the default engine and api key

survos_meiliadmin:
    host: http://localhost:7700
    api_key: 2u24ksdafjj

The adjust the route if necessary, otherwise, open the symfony project project and go to /meiliadmin (or /admin/meili, especially if you have a route rule that block non-admins from that endpoint.

I think this will work, but I wonder in fact if it's the best way.

OSM, Leaflet

Just wanted to let you know that this saved me tons of time not having to develop my own little adminpanel. Love the tool, does exactly what it advertises and was really simple to deploy!

Some ideas:

• Would be nice to be able to manange API keys Edit: Just noticed that key management was already implemented
• Would love if I could change all index settings in one go, on top of specific settings.

https://demo.meilisearchadmin.com/

Meilisearch cloud has also provided a visual management panel, but it is not open source. A continuously updated open source solution is exactly what we need. I will not develop if this project is ready to continue. I will recommend friends to contribute

https://kaermorchen.github.io/meiliadmin/

isn't working for me.

The looks great. Is there documentation somewhere on how to install it?

Thanks.

Hi, first thank you for your package.

I want to know if it's possible to add a pagination or add button to load more data like on the task page.

Thank you

There are some new properties in 1.5 and 1.6 that are showing warnings:

To simplify the process of hosting this service on platforms like Kubernetes, I would like to request the creation of a Docker image and host it on DockerHub

By packaging the service as a Docker image, it becomes easier to deploy and manage across different environments.

In the dashboard, the index name is title-cased. It shouldn't be, as a programmer using that name to get the index may get an error.

If the programmer wants to capitalize the index names, they should, but the UI should display the actual name of the index, not formatted in any way.

The column names should be exactly the same as the data keys:

Hi
I see a validation bug or something is wrong here https://nimb.ws/7fhpjT ?