No description
🚀 (frontend): Implement support for process.env.PORT to run app on a configurable port 🔧 (frontend): Change port variable case from lowercase 'port' to uppercase 'PORT' for better semantics 📝 (frontend): Add comments to clarify the purpose of loading conversation data only when user explicitly selects a conversation 📝 (frontend): Add comments to explain the logic for loading conversation data based on certain conditions 📝 (frontend): Add comments to describe the purpose of handling new conversation creation and resetting messages 📝 (frontend): Add comments to explain the logic for loading conversation data when conversationData changes 📝 (frontend): Add comments to clarify the purpose of loading conversations from the backend 📝 (frontend): Add comments to describe the logic for silent refresh to update data without loading states 📝 (frontend): Add comments to explain the purpose of starting a new conversation and creating a placeholder conversation 📝 (frontend): Add comments to clarify the logic for forking from a response and starting a new conversation 📝 (frontend): Add comments to describe the purpose of adding a conversation document and clearing conversation documents 📝 (frontend): Add comments to explain the logic for using a timeout to debounce multiple rapid refresh calls 📝 (frontend): Add comments to clarify the purpose of cleaning up timeout on unmount 📝 (frontend): Add comments to describe the logic for handling new conversation creation and resetting state 📝 (frontend): Add comments to explain the logic for forking from a response and starting a new conversation 📝 (frontend): Add comments to clarify the purpose of using useMemo for optimizing performance in ChatProvider 📝 (frontend): Add comments to describe the logic for using useMemo in the ChatProvider component 📝 (frontend): Add comments to explain the purpose of the useChat custom hook 📝 (frontend): Add comments to clarify the error message when useChat is not used within a ChatProvider 📝 (services): Update ChatService to fetch Langflow history with flow_id parameter for better control |
||
|---|---|---|
| .github/workflows | ||
| documents | ||
| flows | ||
| frontend | ||
| keys | ||
| securityconfig | ||
| src | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .python-version | ||
| docker-compose-cpu.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Dockerfile.backend | ||
| Dockerfile.frontend | ||
| pyproject.toml | ||
| README.md | ||
| uv.lock | ||
| warm_up_docling.py | ||
OpenRAG
getting started
Set up your secrets:
cp .env.example .env
Populate the values in .env
Requirements:
Docker or podman with compose installed.
Run OpenRAG:
docker compose build
docker compose up
CPU only:
docker compose -f docker-compose-cpu.yml up
If you need to reset state:
docker compose up --build --force-recreate --remove-orphans
For podman on mac you may have to increase your VM memory (podman stats should not show limit at only 2gb):
podman machine stop
podman machine rm
podman machine init --memory 8192 # example: 8 GB
podman machine start