Skip to content
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 Request]: Support more object storage, including s3, azure. #2277

Open
1 task done
baifachuan opened this issue Sep 5, 2024 · 1 comment
Open
1 task done
Labels

Comments

@baifachuan
Copy link
Contributor

Is there an existing issue for the same feature request?

  • I have checked the existing issues.

Is your feature request related to a problem?

I'm not use minio object storage, in production environments, S3 and Azure Blob are used more often.

Describe the feature you'd like

I want to config the S3 or Azure Blob as the object sotrage of ragflow, not MINIO.

Describe implementation you've considered

Both support more storage

Documentation, adoption, use case

You can set the os env:

STORAGE_IMPL=MINIO/AZURE_SPN/AZURE_SAS/S3

to config your object storage.

Additional information

No response

@Said-Apollo
Copy link

Support for GCP buckets would also be great

KevinHuSh added a commit that referenced this issue Sep 9, 2024
…#2278)

### What problem does this PR solve?

issue: #2277

_Briefly describe what this PR aims to solve. Include background context
that will help reviewers understand the purpose of the PR._

### Type of change

- [ ] Bug Fix (non-breaking change which fixes an issue)
- [x] New Feature (non-breaking change which adds functionality)
- [ ] Documentation Update
- [ ] Refactoring
- [ ] Performance Improvement
- [ ] Other (please describe):

Co-authored-by: Kevin Hu <[email protected]>
Halfknow pushed a commit to Halfknow/ragflow that referenced this issue Nov 11, 2024
…infiniflow#2278)

### What problem does this PR solve?

issue: infiniflow#2277

_Briefly describe what this PR aims to solve. Include background context
that will help reviewers understand the purpose of the PR._

### Type of change

- [ ] Bug Fix (non-breaking change which fixes an issue)
- [x] New Feature (non-breaking change which adds functionality)
- [ ] Documentation Update
- [ ] Refactoring
- [ ] Performance Improvement
- [ ] Other (please describe):

Co-authored-by: Kevin Hu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants