Add npm package publication for mongodb-rag-core, mongodb-rag-ingest, mongodb-chatbot-server
Drone action to publish on tag creation on github.
release-it configuration to create release notes per package on publication.
Refactor package co-dependencies to follow Lerna best practices for importing local packages that are also published
Split chatbot-server-mongodb-public from chat-server for deployment of our implementation of mongodb-chatbot-server
Convert mongodb-chatbot-server into npm package that others can use
Notes
As part of this work, mongodb-rag-core, mongodb-rag-ingest, mongodb-chatbot-server are all live on npm.
Didn't do npm package publication CI for chat-ui. didn't want to break anything that nick and DOP depend upon.
In future work, we should doing the following:
renaming all directories to match their package names for clarity (eg chat-core -> mongodb-rag-core)
rename mongodb-chatbot-server package to mongodb-rag-server
Food for thought: merge mongodb-rag-core, mongodb-rag-ingest and mongodb-chatbot-server into single npm package called "mongodb-rag" with /imports (eg import {foo} from "mongodb-rag/server").
this isn't strictly necessary but would make dependency management way easier. like would have made the work i did this take way less time.
think could also help unify the narrative on this being 1 single mongodb RAG framework.
Jira:
Changes
chat-coreinto npm packagemongodb-rag-coremongodb-rag-core,mongodb-rag-ingest,mongodb-chatbot-serverchatbot-server-mongodb-publicfromchat-serverfor deployment of our implementation ofmongodb-chatbot-servermongodb-chatbot-serverinto npm package that others can useNotes
mongodb-rag-core,mongodb-rag-ingest,mongodb-chatbot-serverare all live on npm.chat-ui. didn't want to break anything that nick and DOP depend upon."mongodb-rag"with/imports(egimport {foo} from "mongodb-rag/server").