Add a .dockerignore for the client build context
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, javascript
- Domain
- build-system
Research direction
Start by reviewing the client Docker build inputs and the existing repository-root .dockerignore, then inspect src/Dome.Client to identify generated files and local metadata. Add src/Dome.Client/.dockerignore with the listed exclusions, checking that files needed by npm ci and npm run build remain in the context. Done when the context excludes the specified generated files and the client Docker build succeeds from a clean checkout.
Written by the indexing model from the issue text.
Description
Summary
The client image uses src/Dome.Client as its Docker build context. The repository-root .dockerignore does not apply to this separate context, so frontend-generated or local files inside the client directory may be sent to the builder unnecessarily.
Proposed change
Add src/Dome.Client/.dockerignore with appropriate exclusions, at minimum:
node_modules/
dist/
coverage/
.vite/
.git/
*.log
Review the actual client build inputs before adding any further exclusions.
Acceptance criteria
- The client Docker build context excludes generated dependencies, build output, coverage output, and local Git metadata.
- The Docker build still succeeds from a clean checkout.
- The change does not exclude files required by
npm ciornpm run build.
- Dominant language
- C#
- Stars
- 0
- Forks
- 2
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 28
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from Dome-Works/DOME
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Dome-Works/DOME#128 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Dome-Works/DOME#126 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Dome-Works/DOME#127 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Dome-Works/DOME#123 ·
Maintainers usually reply within 1 day
-
Implement container update for managed stacks when update is available.Possibly taken @MathijsNabbe claimed this 10 days ago. Openenhancement
Dome-Works/DOME#117 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 優先: 低
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
.NET area: storage bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Larson-Logan/medal-sync#61 ·
Maintainers usually reply within 1 day