Great to see that Ploi has an option to create Meilisearch servers! However, after testing it out, I decided to install it manually on a plain server after all, because I was missing some options. I share this feedback, hoping that this will be useful if you'd like to beef out Ploi's Meilisearch integration.

The options I was missing:

1. Option to create system user, and use this user to run meilisearch
2. Option to specify the location for dumps, snapshots, config.toml, and meilisearch executable
3. Option to apply configs via a configs.toml file (as supported by Meilisearch) instead of flags on the executable in the systemctl meilisearch.service (also preventing customizations to the meilisearch.service from getting overwritten everytime)
4. Option to pick from all available actions when generating keys (the list in the UI is incomplete)
5. This one I'm not 100% sure is missing, but I couldn't see any option to migrate Meilisearch to the latest version via the UI (might be a complex one though)
6. The option to have Meilisearch run on DigitalOcean's internal IP, without it causing errors in the "indexes" and "keys" tab (could not connect to server)
7. Some more assistance for setting up SSL

The features provided by Ploi right now are good for setting up Meilisearch in the most default configuration, but it could be buffed out with some additional details. For example, I would love to see a status tab, with availability, engine version, info on (failed/pending/running) tasks and batches, experimental feature enabled/disabled status, etc. Also, the indexes tab could have a nice feature where you can click on the index, and see the stats and settings for that index.

Again, this is meant as supportive feedback. I really appreciate the work you're doing, and hope to see it grow bigger and better. Hope this helps.