docs(dev): align setup with current stack

This commit is contained in:
cesnimda
2026-08-30 11:32:00 +02:00
parent 16ef3b9463
commit 2d7a51c3fd
10 changed files with 104 additions and 78 deletions
+5 -21
View File
@@ -65,29 +65,14 @@ EMAIL_FOLLOWUPREMINDERS_UPCOMINGDAYS=2
SUMMARIZER_BASE_URL=http://ai-service:8001
```
## Database recommendation
For production, yes — use a real database.
## Supported databases
### Recommended direction
Short term:
- SQLite is acceptable for a single-user or very small deployment
- keep backups and volume persistence
The application supports only these provider values:
Better production choice:
- MariaDB or PostgreSQL
- `sqlite` — local development and small single-instance deployments; persist and back up the data volume.
- `mariadb` or `mysql` — server deployments through the Pomelo EF Core provider. The production example uses MariaDB.
### My recommendation
- **PostgreSQL** if you want the best long-term maintainability and fewer edge cases
- **MariaDB** is also fine if that is what you already know or host elsewhere
If you stay on SQLite:
- okay for small personal use
- not ideal for concurrent writes, larger scale, or operational robustness
## Practical recommendation for this project
If this app is going to be a real production service on Ubuntu:
- move to PostgreSQL first if possible
- MariaDB is still a reasonable option if preferred
PostgreSQL is not implemented. Do not configure or recommend it without first adding an EF Core provider, migrations, startup validation, backup/restore support, and a provider test matrix.
## Deployment flow
@@ -117,7 +102,6 @@ if forwarded-header trust is enabled without a valid known CIDR.
- confirm AI service container is reachable from backend
- confirm reminder and admin/system pages load
- verify follow-up reminder emails are enabled only when intended and that links open the correct job/tab
hat links open the correct job/tab
---