-
-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/2 seed rag web UI with unep documents #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/2 seed rag web UI with unep documents #3
Conversation
docker-compose-wgprtm.dev.yml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why we have this? if you think it's important or make easier for development (not only you), please add this changes directly to dev.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created a separate Docker Compose file because some of the ports defined aren't available on my local environment, and also to use a compatible ChromaDB Docker image for my ARM64 architecture.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then move the ChromaDB image to .env
data-pipeline/unep/knowledge_unep.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of data-pipeline, "script" is more generic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so the path can be script/kb_init_unep.py
docker-compose-wgprtm.dev.yml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then move the ChromaDB image to .env
Uh oh!
There was an error while loading. Please reload this page.