cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(database): record MariaDB qualification and retirement gates
MariaDB persistence qualification / mariadb (push) Failing after 1m7s
Details

Browse Source
This commit is contained in:
cesnimda
2026-10-24 01:52:03 +02:00
parent a2c9bda0d1
commit e75c4a4775
20 changed files with 14568 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuration/environments.md
+8 -2
View File
@@ -2,11 +2,17 @@
## Local development
SQLite and localhost defaults are supported. Run the API on 5202 and the UI on 3000, or use the development Compose override. Use seeded development credentials only from local settings and never reuse them in production.
MariaDB is the standard. Start the isolated persistent service in `docker-compose.database.yml`,
then run the API on 5202 and UI on 3000. Development settings use only loopback port33306 and
development-only credentials. See [MariaDB setup](../database/mariadb-standardisation/README.md).
Explicit SQLite selection is temporary for existing data and legacy test fixtures; it is never an automatic fallback.
## Tests
Jest, Playwright, xUnit, and the Python tests create isolated fixtures or temporary databases. They may set test-only variables such as `AI_SERVICE_SKIP_MODEL_LOAD`; they must not use a real database, mailbox, provider key, or production URL.
Jest, Playwright, xUnit and Python use isolated fixtures. The MariaDB integration lane uses an actual
disposable local server and creates only generated `jt_it_*` schemas. Never use an existing user or
production database, mailbox, provider key or production URL. Legacy SQLite/InMemory tests remain
explicitly labelled transition evidence and cannot substitute for MariaDB qualification.
## Production