RECORDGOD/.dockerignore
type-two 5ebb997978 security(pii): keep customer SQL dumps out of git and the Docker image
customers.sql (610KB phpMyAdmin dump: wp_rmp_users password hashes + real
customer names/emails/phones/addresses) sat untracked but matched NEITHER
.gitignore NOR .dockerignore, and Dockerfile does COPY . . — so it was one
'git add .' from history and already bakeable into the public image.

- .gitignore:  customers*.sql  (schema.sql stays tracked)
- .dockerignore: *.sql  (startup DDL is inline in app/main.py; no .sql needed at runtime)

Working-tree customers.sql shredded. site-update.sql was already gitignored;
now dockerignored too.

NOTE: rebuild+redeploy the image to purge copies already baked into layers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 02:04:45 +10:00

18 lines
538 B
Plaintext

.venv/
.git/
__pycache__/
*.pyc
.env
disc_images/
# NOTE: do NOT exclude webstore/ — main.py mounts /store from it (the 3D virtual store).
# Only disc_images/ (~900MB, volume-mounted at runtime) is worth excluding from the build context.
*.md
# distro raw dumps — never bake supplier PII / account tokens into the image
ingest_raw/
rarw*.txt
inertia.txt
*.xlsx
# SQL dumps — customer/order PII + WP password hashes. Never bake into the image;
# the app's startup DDL is inline in app/main.py, so no .sql is needed at runtime.
*.sql