[FEAT-API]: Refactor Dockerfiles and docker-compose files
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The amount of docker-compose... files and Dockerfiles in the api are starting to compound.
Lets look into if there is a better way to organize them that:
- follows best practices
- allows for flexibility if more images need to be added
- is readable and easier to manage
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 inventorying the API's Dockerfiles and docker-compose files referenced in the issue, then review how their images and environments are currently organized. Done means the container configuration follows clear best practices, remains flexible for adding images, and is easier to read and manage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100