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

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
+11 -2
View File
@@ -6,7 +6,7 @@ Job Tracker (Jobjakt) is a self-hosted workspace for managing job applications,
- Next.js 16 / React 19 / TypeScript / MUI frontend
- ASP.NET Core 9 / EF Core 9 API
- SQLite by default; MariaDB/MySQL for server deployments
- MariaDB across development, integration testing, CI and production; SQLite retained only during staged retirement
- FastAPI document/AI service with optional Ollama, Gemini, or Groq CV routing
- Docker Compose + nginx; Gitea Actions deployment
@@ -22,7 +22,15 @@ docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build
Open `http://localhost:3000`. The API is available at `http://localhost:5202` in local process development.
For local processes:
For local processes, start the separate persistent development database first:
```powershell
docker compose -f docker-compose.database.yml up -d --wait mariadb-dev
```
Then run the API/UI below. Development settings use only the loopback `jobtracker_dev` database;
startup applies the existing migrations. [MariaDB setup and qualification](docs/database/mariadb-standardisation/README.md)
documents the pinned server, disposable integration lane, credentials and data-preservation rules.
```powershell
cd JobTrackerApi
@@ -38,6 +46,7 @@ npm run dev
```powershell
dotnet test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --no-restore
python scripts/mariadb-integration.py
cd job-tracker-ui
npm run lint
npm test -- --runInBand