Allow for separate blob stores for one project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 595
- Forks
- 101
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 1
Description
Currently, a Vercel project can only link to a single Blob Store with a unique prefix. This prevents the common practice of using separate storage for different environments (e.g., staging vs. production) within the same project.
It would be ideal to allow a project to use different blob stores based on the environment, similar to how one might use separate S3 buckets.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named in the issue. Start by locating the project configuration and Blob Store integration, then trace how the current unique prefix is selected. Done means one project can use distinct Blob Stores for different environments, such as staging and production.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100