anyproto / anyproto/any-sync-dockercompose
Provider-agonostic S3 store config
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 941
- Forks
- 134
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 3
Description
Have you read a contributing guide?
- I have read CONTRIBUTING.md
- I have searched the existing requests and didn't find any that were similar
- I have considered creating a pull request instead and want to proceed
Clear and concise description of the problem
Aside of #178, maybe we can only set connection credentials, thus supporting any S3-compatible storage and avoiding vendor lock-in. It also makes using a shared AIStor instance possible.
Suggested solution
Accept S3 connection credentials. If provided, don't setup MinIO.
Alternative
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Docker Compose configuration and the existing MinIO setup, then review issue #178 for related context. Trace how storage connection settings are currently supplied and determine where external S3 credentials would be accepted. Done means credentials can configure an S3-compatible provider without setting up MinIO, with the existing configuration behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100