Problem/Motivation

I had .ddev/docker-compose.milvus.yaml which was copied from vdb_providers/vdb_provider_milvus/docs/docker-compose-examples/ as per instructions at https://project.pages.drupalcode.org/ai/modules/vdb_providers/vdb_provid...

Now this file is gone in the new 1.0.0 release.
I've looked at docs/ddev-examples, it's not there.

Please elaborate, was it removed intentionally or not?
Does it mean it's no longer supported?
Or this can be still maintained?

Comments

kenorb created an issue. See original summary.

kenorb’s picture

kenorb commented
Issue summary: View changes
z3cka’s picture

z3cka commented

I found it!

https://git.drupalcode.org/project/ai/-/blob/532368346d7888d52f981bb3b1d...

Looks like it was removed sometime from now and 5 months ago. I'm testing it now to see if it still works. I will report back how it goes.

marcus_johansson’s picture

marcus_johansson commented
Project: AI (Artificial Intelligence) » Milvus VDB Provider
Version: 1.0.0 » 1.0.x-dev

I think we should probably create a DDEV plugin for Milvus, so there is a more official local development solution for it and then for production, people have to readup themselves on how to set it up optimally.

WDYT?

Moving the issue to the provider issue queue as well.

z3cka’s picture

z3cka commented

I think that is a great idea.

As for a follow up on the old ddev yaml; it seems to set up a Milvus service, but I quickly ran into issue #3410946. So, I didn't get very far.

scott_euser’s picture

scott_euser commented
Status: Active » Closed (outdated)

It seems the idea of making a DDEV Plugin should be a separate follow-up I think right?

But the docs to address this particular issue summary for ddev milvus docker compose are here at least for this particular issue (and recently updated) https://git.drupalcode.org/project/ai_vdb_provider_milvus/-/tree/1.1.x/d... so will close

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.