feat: use client server
Added an optional client-only mode, so that you can run a chromadb-server separately. Regards #116. Is in the interest of #75 as well.
This is useful for scalability. Say you have EmbedChain behind an API with multiple workers (I think this is how it's going to be in most production environments). If you separate clients and server, all clients can connect to the server, which only has to keep one instance of the database in memory. You also don't have to worry about adding embeddings while it's live.
I also hope it helps with the persistence issue.
This also makes it easier to add a fullstack example with docker in the future.
In the readme I added an advanced section for this and future more advanced options we provide.
Brilliant! Data persistency is something I'm missing too atm
updated to work with the new config