RECORDGOD/.gitignore
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

17 lines
484 B
Plaintext

__pycache__/
*.pyc
.env
.venv/
venv/
# distro raw dumps — saved scrapes/spreadsheets for manual ingest. Never commit:
# they carry supplier PII + live account tokens (e.g. a RareWaves buyer JWT). Local-only.
ingest_raw/
rarw*.txt
inertia.txt
*.xlsx
# live-site MariaDB dumps for 3D-store/editor data work — full site export, carries customer/
# order PII. Local-only; another lane consumes it for robotmonster.party/store racks + editor.
site-update.sql
customers*.sql
*-dump.sql