rikrdo/arnes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

F-003 fix: Sanitize SQL dump for safe dev use

Browse Source
This commit is contained in:
rikrdo
2026-05-25 08:14:34 +02:00
parent 3d41579ad3
commit e6feea5ee6
24 changed files with 483 additions and 1187942 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
spec/sdd/components/development-data-baseline.md
View File

@@ -1,24 +1,25 @@
# Component: Development data baseline
## Responsibility
Provide one local SQL dump so maintainers can inspect schema and seed dev database.
Provide one safe local SQL baseline so maintainers can seed a development database for the legacy PHP module.
## Interfaces
- Input:
- SQL import command run by maintainer
- Output:
- local MariaDB database with OpenCart and custom tables
- local MariaDB database with the schema and synthetic seed data needed by the module
## Dependencies
- `project/sql/db-25052026.sql`
- `project/sql/README.md`
- local MariaDB/MySQL server
## Limits
- Dump may contain production-like data.
- Dump is large.
- Dump is not safe for public sharing without review.
- Baseline is intentionally smaller than the former raw snapshot.
- Baseline covers current module needs, not the full production dataset.
- Private raw snapshots must stay outside git.
## Success criteria
- [ ] Dump path is stable and explicit
- [ ] Design docs call it dev baseline only
- [ ] Move does not alter dump content
- [ ] Tracked dump contains only safe synthetic or non-sensitive data
- [ ] Docs explain private local dump handling