NYCPlanning / NYCPlanning/data-engineering
Number of DE docker images
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
problem
We maintain five docker images and nearly as many text files related to python package requirements for those images (Docker images wiki section). The potential benefits of maintaining this many distinct images and requirements files seems outweighed by the complexity.
To focus this issue on improving DE's work, the more public-facing docker-geosupport image can be excluded from any thoughts/changes here.
questions
- Does the
build-geosupportimage need it's own requirements file? - Why can't all of the images use
admin/run_environments/requirement.txt? - Is it important to keep geosupport out of our
build-baseimage?
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 with the Docker images wiki section and inspect the image definitions and requirements files, including admin/run_environments/requirement.txt. Compare the build-geosupport and build-base images and determine how their dependencies are maintained. Done means reaching and documenting a clear decision about which images and requirements files should remain, excluding docker-geosupport.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100