readthedocs / readthedocs/common
Configuration for public/private storage policies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 48
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 5
Description
In #144, we moved the configuration of MinIO storage bucket policies to a process related to initialize the web container. This was a kind "configuration as code" chosen over the manual setup from before.
Some buckets are private, depending on the environment. This should be expressed as configuration somewhere.
https://github.com/readthedocs/common/pull/144#discussion_r898097442
https://github.com/readthedocs/common/pull/144#discussion_r898097826
This issue might be solved in a way that only affects the docker setup, and if possible/necessary can be integrated for other deployments as well.
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
Start by reading PR #144 and the two linked discussion comments, then trace the process that initializes the web container's storage policies. Define how private buckets vary by environment and verify that the configuration is applied in the Docker setup, with any broader deployment integration explicitly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100