willnorris / willnorris/imageproxy
Feature request: GridFS provider support (MongoDB) for image sources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 513
- PR merge metrics
- No merged PRs in 30d
Description
It would be very useful to add GridFS (MongoDB) as a supported image source/provider for imageproxy.
In many production setups, images are stored in MongoDB GridFS rather than on disk or in S3-compatible storage. Native GridFS support would allow imageproxy to be used directly as an image delivery and transformation layer without introducing an additional proxy or sync layer.
Related links
- MongoDB GridFS documentation: https://www.mongodb.com/docs/manual/core/gridfs/
- MongoDB Go Driver (GridFS): https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo/gridfs
If this approach is acceptable, I am willing to fully implement the feature, including code, tests, and documentation.
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 reading the MongoDB GridFS documentation and the Go Driver GridFS package linked in the issue, then locate imageproxy’s existing image source/provider entry points. Define how GridFS configuration, retrieval, errors, tests, and documentation should fit the project; the feature is done when those decisions are implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, mongodb
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100