Created on 26 January 2024, over 1 year ago

I have created a DDEV addon for running Meilisearch locally:

https://github.com/kevinquillen/ddev-meilisearch

It has an admin UI, saves from having to set up a cloud interface to do development or testing.

💬 Support request
Status

Active

Version

2.0

Component

User interface

Created by

🇺🇸United States kevinquillen

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kevinquillen
  • 🇸🇮Slovenia bcizej

    Nice thanks, although I use custom docker-compose.yml, other contributors here use a DDEV setup with custom meiiisearch service added, this comes in handy to get the environment up and running easily.

    I'll update the readme when I get the chance, it is missing a section for development (setting up, running automated tests. etc), and include the link to the addon.

  • First commit to issue fork.
  • @deaom opened merge request.
  • 🇸🇮Slovenia bcizej

    @deaom I don't understand this PR. Why would the module include DDEV setup? This issue was suppose to just add info to the readme on how to add meilisearch service locally for testing (either by using docker image or if using DDEV - to use Kevin's plugin).

    Also why was the issue text updated with all that? Was that a mistake and was supposed to be a comment?

    Anyway, this PR is above what it was suppose to do, moving back to needs work.

  • 🇸🇮Slovenia deaom

    Maybe it would be best if I opened a new issue in regards to that to not cause confusion. But basically as Drupal community selected DDEV as a recommended local development environment - https://www.drupal.org/docs/getting-started/installing-drupal/install-drupal-using-ddev-for-local-development a ddev add on was created for easier local development of contributed modules.
    The ddev-drupal-contrib recommends committing the .ddev folder. Some projects do have that added, some do not as it is of course up to the maintainer of the module to actually decide to include it or not.
    It could also be just a note in the documentation on how to do it. Again, up to you, the maintainer.
    The PR can be closed out.

Production build 0.71.5 2024