Full mariadb-dump (schema + data) from the live develop instance,
post-NFP-18 migration. Includes test data new devs can immediately
poke at instead of staring at an empty dashboard.
Contents:
- 36 tables (full schema)
- 2 users (admin@finetune.ai/admin123, testuser@example.com/test123)
- 5 datasets, 1 job (Support Bot v1, completed), 1 model
- 1 user_billing row, 5 user_settings rows
- 8 email_templates, 3 ACL roles, all migrations table state
Sanitization applied at the end of the dump (POST-LOAD block):
- user.user_pass set to NULL (legacy AES-encrypted passwords;
post-NFP-18 auth uses user_password_hash only)
- user_settings values for keys matching token/key/secret/password/api
set to empty string (devs add their own HF token, etc.)
- user_password_hash for both default users reset to freshly-generated
argon2id hashes that verify against the documented plaintexts
bootstrap-db.sh adds NFP_USE_SNAPSHOT=1 to load this instead of the
clean 3-file path. Both routes arrive at the same credentials.
Verified end-to-end:
- dump loads on a fresh DB (exit 0)
- both default credentials authenticate via password_verify
- all data rows preserved
- no credential-shaped strings in non-comment lines
The user_to_acl table is one of the few join tables that does NOT follow
the tablename_fieldname column naming convention — its columns are the
plain `user_id` and `acl_id`. The previous version used `user_to_acl_user_id`
and `user_to_acl_acl_id` which fail with "Unknown column".
Found by actually running bootstrap-db.sh end-to-end against a fresh DB
(was missing this verification step on the initial commit).
Verified now:
- schema loads cleanly (36 tables)
- seed loads (3 ACL roles, 8 email templates)
- default users insert + ACL mapping works
- password_verify against argon2id hashes confirms admin123 and test123
Generated from finetuning-plattform develop @ 70b203c on 2026-05-14.
Contents:
- MANUAL.md — full developer manual, setup at front (28 sections)
- bootstrap-db.sh — one-command DB initialization
- db/01-schema.sql — MariaDB schema, no data
- db/02-seed.sql — reference data (ACL, email templates, API registry)
- db/03-default-users.sql — admin + test user, argon2id hashes
Drop-in package for new developers joining the platform.