[FEAT-API]: Refactor Dockerfiles and docker-compose files

Open
#641 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker, docker-compose
Domain
devops

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.

Description

The amount of docker-compose... files and Dockerfiles in the api are starting to compound.

Image

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
Dominant language
No language data
Stars
2
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from USACE/chart-docs

All issues in USACE/chart-docs

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.