Skip to content

fix(docker): add .dockerignore to tighten build context #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DavidHLP wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(docker): add .dockerignore to tighten build context #109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 58 additions & 0 deletions .dockerignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
# === .dockerignore for UltiCode monorepo ===
# Build contexts: console/, management/, backend-spring/ (each COPYs shared/).
# Keep those dirs and their build inputs; exclude everything else so the
# context sent to the daemon stays small and free of local secrets.

# VCS & CI metadata
.git
.gitignore
.github
.gitlab

# IDE / agent tooling
.claude
.cursor
.codex
.agents
.vscode
.idea

# Docs & knowledge base (not needed by image builds)
wiki
docs
*.md
!README.md

# Build artifacts & caches (regenerated inside the image)
**/node_modules
**/dist
**/.vitest
**/coverage
**/target
**/.turbo

# Logs & runtime ephemera
**/*.log
logs
**/logs
**/.pids

# Local dev secrets & runtime (NEVER bake into images)
.env
.env.*
Comment on lines +41 to +42

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 5, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Exclude nested dotenv files from Docker context

When a developer builds the console or management images from a checkout containing console/.env.local, console/.env.production.local, or similar app-local dotenv files, these patterns only cover dotenv files at the root of the build context; the Docker docs note that a bare glob such as *.md applies only right under the context directory. Since the frontend Dockerfiles use COPY console ./console / COPY management ./management before pnpm build, those local env files can still be sent to the daemon, stored in build cache, or influence the Vite bundle. Use recursive patterns such as **/.env and **/.env.* with explicit example-file exceptions.

Useful? React with 👍 / 👎.

!.env.example

# Tooling not used by app images
infrastructure
tools
scripts
tmp
.tests

# Deploy orchestration (not part of any image)
docker-compose*.yml
ecosystem.config.cjs

# Standalone images with their own build contexts
init-db
docker/sandbox