2023fdc13e
fix file preview in file management (#1151)
### What problem does this PR solve?
fix file preview in file management
### Type of change
- [x] Bug Fix (non-breaking change which fixes an issue)
il y a 1 an
7e41b4bc94
change readme for 0.3.0 release (#459)
### What problem does this PR solve?
### Type of change
- [x] Documentation Update
il y a 1 an
b3843138f4
change version number in readme (#390)
### What problem does this PR solve?
### Type of change
- [x] Documentation Update
il y a 1 an
9e75bd4d88
change version number (#368)
### What problem does this PR solve?
Issue link: for release v0.1.0
### Type of change
- [x] Documentation Update
- [x] Refactoring
il y a 1 an
5c62b993f2
refactor (#358)
### What problem does this PR solve?
Issue link:#350
### Type of change
- [x] Refactoring
il y a 1 an
446195fa81
remove version top-level element in the compose.yml file (#349)
### What problem does this PR solve?
- remove version top-level element in the compose.yml file
when use command `docker compose -f docker-compose-CN.yml up -d` ,it
will waring,[maybe it appear after
v25,5](https://github.com/mailcow/mailcow-dockerized/issues/5797#issuecomment-2011349228 )
ref to
https://docs.docker.com/compose/intro/history/#docker-compose-cli-versioning
> Version one of the Docker Compose command-line binary was first
released in 2014. It was written in Python, and is invoked with
docker-compose. Typically, Compose V1 projects include a top-level
version element in the compose.yml file, with values ranging from 2.0 to
3.8, which refer to the specific [file
formats](https://docs.docker.com/compose/intro/history/#compose-file-format-versioning ).
> Version two of the Docker Compose command-line binary was announced in
2020, is written in Go, and is invoked with docker compose. Compose V2
ignores the version top-level element in the compose.yml file.
Also in `README.MD` show `Docker >= 24.0.0 & Docker Compose >= v2.26.1`.
so i want to remove the version.
### Type of change
- [x] Other (please describe):
remove warning
il y a 1 an
84d7a006dd
add hf_endpoint as env variable (#353)
### What problem does this PR solve?
Issue link:#350
### Type of change
- [x] Refactoring
il y a 1 an
91068edf16
Support Xinference (#320)
### What problem does this PR solve?
Issue link:#299
### Type of change
- [x] New Feature (non-breaking change which adds functionality)
il y a 1 an
3708b97db9
Support Ollama (#261)
### What problem does this PR solve?
Issue link:#221
### Type of change
- [x] New Feature (non-breaking change which adds functionality)
il y a 1 an
23b448cf96
fix docker compose issue (#238)
### What problem does this PR solve?
_Briefly describe what this PR aims to solve. Include background context
that will help reviewers understand the purpose of the PR._
Issue link:#[[Link the issue
here](https://github.com/infiniflow/ragflow/issues/226 )]
### Type of change
- [x] Bug Fix (non-breaking change which fixes an issue)
il y a 1 an
121c7a5681
refine error response, add set api-key MD (#178)
il y a 1 an
8a57f2afd5
change callback strategy, add timezone to docker (#96)
il y a 1 an
e86c820461
resolve user login issue, and docker confiuration issue (#84)
il y a 1 an
320cbf545f
docker debugging modification (#82)
il y a 1 an
39269d2f79
add dockerfile and fix trival bugs (#78)
il y a 1 an
30791976d5
build python version rag-flow (#21)
* clean rust version project
* clean rust version project
* build python version rag-flow
il y a 1 an
1eb186a25f
go through smoke test of all API (#12)
* add field progress msg into docinfo; add file processing procedure
* go through upload, create kb, add doc to kb
* smoke test for all API
* smoke test for all API
il y a 1 an
249b27c1e0
go through upload, create kb, add doc to kb (#11)
* add field progress msg into docinfo; add file processing procedure
* go through upload, create kb, add doc to kb
il y a 1 an
738c322508
add docker compose (#8)
* add docker compose
* add docker compose
il y a 1 an
KevinHuSh
ooo oo