[Question]: Upgrade Procedures and Multi-Volume Management in RAGFlow
Describe your problem
I'm using RAGFlow in some test projects, and a question has arisen. While other frameworks offer documentation on standard procedures for version upgrades, I haven't found anything similar for RAGFlow.
Currently, I'm using the full Docker image and couldn't locate specific guidance on how to properly manage volumes, considering that the project uses multiple volumes. What would be the recommended approach to handle this? Is there any future plan to provide detailed upgrade documentation?
Documentation is a good suggestion.
No influence to local volumes by upgrading system. If it will, we will claim that in release note.
BTW: Never docker compose down -v which will remove all the local data.