Skip to content
This repository was archived by the owner on May 10, 2024. It is now read-only.

Conversation

jarqvi
Copy link

@jarqvi jarqvi commented Feb 4, 2024

I feel like this can be useful

Copy link

vercel bot commented Feb 4, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 4, 2024 8:10am

@jeffchuber
Copy link
Contributor

@tazarov can you take a look here?

Copy link
Contributor

@tazarov tazarov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffchuber, this looks fine, but I wonder if it makes DX better or worse by having to create/manage additional volume as opposed to local dir bind?

```sh
docker pull chromadb/chroma
docker run -p 8000:8000 chromadb/chroma
docker volume create chroma-data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarqvi, in your experience, why do you think this is better than local dir binding (-v ./chroma-data:/chroma/chroma)? Is it better for developer experience to create a separate volume?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I usually use volumes to store container data and bind mounts to configure or dynamically change the container.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants