From fabdff3bef8f187e7140fdff05a27fc4eb93db4c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Trkan?= Date: Sun, 16 Nov 2025 17:27:13 +0100 Subject: [PATCH] update checklist --- 7project/checklist.md | 4 +-- todo.md | 61 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 63 insertions(+), 2 deletions(-) create mode 100644 todo.md diff --git a/7project/checklist.md b/7project/checklist.md index cdf605e..4ec4eb6 100644 --- a/7project/checklist.md +++ b/7project/checklist.md @@ -29,8 +29,8 @@ This means that you must get at least 2 points for each item in this category. | | Advanced features implemented | 10 | 5 | OAuth, BankAPI connection (not only mock bank) | | | Error handling & robustness | 10 | 5 | App notifies user about errors, errors in code are also logged by sentry and we get notified | | 24 | User-friendly interface | 5 | 4 | Responsive interface with dark mode support, should by user friendly enough | -| Backend & Architecture | Stateless web server | 5 | 0 | Our server is stateful TODO: v tomhle mám furt bordel | -| | Stateful application | 10 | 10 | Our server is stateful TODO: v tomhle mám furt bordel | +| Backend & Architecture | Stateless web server | 5 | 5 | Yes, the web server is stateless - authentification uses JWT, not sessions. | +| | Stateful application | 10 | 10 | Yes, the app is stateful - data are persistently stored in database | | | Database integration | 10 | 10 | We have deployed 3 MariaDB nodes with replication, MaxScale proxy and periodic backups. Connection app with this setup is same as with standalone db. | | | API design | 5 | 5 | Backend APIs are implemented with public Swagger docs | | 28 | Microservices architecture | 10 | 3 | We have separated API deployment and worker deployment. Worker process slow tasks - emails, payment scraping. There is no need for another service in current state but adding it is easy. | diff --git a/todo.md b/todo.md new file mode 100644 index 0000000..92addb0 --- /dev/null +++ b/todo.md @@ -0,0 +1,61 @@ + - sentry for error tracking + +- github actions for ci/cd +- deployment using helmchart, prod + dev +- celery background tasks +- cron +- cloudflare tunnels +- mariadb operator for database, maxscale 3 nodes, phpmyadmin, maxscale ui, backups +- prometheus + grafana dashboards for monitoring +- rabbitmq message queue +- longhorn for file storage (edited talosos deployment) + +Aplikace: + +- umíme oauth - mojeid, bankid => oboje se používá i pro autorizaci komunikace s CZ státem +- automatický import plateb z banky +- ukázat frontend +- ukázat backend - oauth, celery tasky, +- alembic na migrace db +- sentry integrace + +Infrastruktura: + +- běžíme na proxmoxu +- kubernetes cluster přes TalosOS jako virtuálky with edited configs +- deployment služeb přes tofu/terraform + - longhorn pro persistentní storage + - mariadb operator s maxscale - 3 nody + phpmyadmin + - prometheus + grafana monitoring + - rabbitmq message queue pro background tasky + - veřejný přístup přes cloudflare tunnels +- ukázat headlamp map +- build v github actions +- deployment pomocí helmchartu prod + dev prostředí pomocí selfhosted runneru +- remote access do clusteru přes tailscale +- + +Where to put description of infrastructure components? for example Helm chart of app is quite large +How about readme? + +linking commits in time table? I cant link all of them - many of them was directly to main branch + +- for example iterative CI/CD setup + +done +create src in 7project +make the chart vertical +urls as hyperlinks text +frontned npm run dev as codeblock +describe folder structure in readme in 7project +add comment column to checklist +readme in src folder with folder structure description +readme in src/tofu +readme in src/charts +add link to report for app +write few lines in Build intructrions, deployment instructions like in testing + + +add other services in cluster in report architecture overview + +debug commands - kubectl logs -f podname, mention grafana