Krzysztof kuhy Rudnicki
50263f075a
`pre-commit run --all-files` is green. The config only carries hooks whose subject is already clean, so it stays green at every commit -- file-length, ruff/mypy and dependency-freshness are listed as blocked, each on its own cleanup, and the file-REWRITING hooks (trailing-whitespace, end-of-file-fixer) are held back for their own reviewed commit. Turning it on found four real things: 1. A committed private key: ERSMS-project/nginx/ssl/nginx.key. It is a self-signed CN=localhost cert that had already expired (notAfter 2025-06-16), so the risk is nil -- but it is regenerable in one openssl call, so it is replaced by generate-cert.sh rather than excluded from the hook. The script says plainly that removing it from HEAD does NOT unpublish it: history is deliberately not rewritten, which is acceptable only because nothing ever trusted this key. 2. Four files with unresolved merge conflict markers committed, left over from the subtree merges. EARIN/.gitignore and .vscode/extensions.json are resolved as the union of both sides. The two Unity folder .meta files each had two candidate GUIDs; grepping showed neither is referenced anywhere (folder GUIDs rarely are), so either is safe and the HEAD side is kept -- an arbitrary choice, but a checked one rather than a guess. 3. 62 shellcheck findings across 11 scripts, all fixed, no disables added. The interesting pattern was `cd X; cmd &; PID=$!; cd ..`, which trips both SC2164 and SC2103 and cannot use a plain subshell without losing the PID. `( cd X && exec cmd ) &` keeps the directory, the PID and the semantics. EOPSY lab1's submitted solution was verified by RUNNING it afterwards: a->A, B->b, foldera->FOLDERA, FOLDERB->folderb, exactly as before. 4. check-json failing on 11 files, which was the wrong parser rather than a defect -- tsconfig*.json and .vscode/*.json are JSONC, where TypeScript and VS Code both allow comments. Those two path classes are excluded and every other .json is still checked. Excluding them is what surfaced the merge conflict in (2) as the one genuine failure. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172dj34FDpao6wsix8ZuCzE |
||
|---|---|---|
| .. | ||
| analytics | ||
| backend | ||
| connector | ||
| database | ||
| docs | ||
| frontend | ||
| movie_recommendations | ||
| nginx | ||
| test_scripts | ||
| .gitignore | ||
| docker-compose.yml | ||
| Dockerfile | ||
| README.md | ||
Projekt z ERSMS
Backend
budowanie i uruchamianie obrazu z bazą danych oraz serwerem:
docker compose up
w przypadku zmian w bazie danych, usunąć kontener oraz dołączone do niego volumy
stronka administracyjna do bazy danych
Najpierw wpisujemy w przeglądarce http://localhost:8080/ Przy logowaniu wpisujemy:
- login - admin@admin.com
- hasło - admin
Po zalogowaniu się poraz pierwszy od zbudowania obrazu, widzimy stronę główną. Klikamy na niej duży przycisk "Add New Server" i pojawia się okienko z menu dodawania serwera.
W nazwie można napisać cokolwiek, jednak w zakładce "Connection" piszemy następujące rzeczy:
- host name - db
- login - root
- password - root
Reszta pozostaje jak była. Po zapisaniu ustawień, mamy już dostęp do narzędzi administratora dla naszej bazy danych.
gadanie z endpointami
GET http://localhost:8090/ - testowy domowy
GET http://localhost:8090//api/v3/get/string:username - info o userach
GET http://localhost:8090//api/v3/get_movie/int:movie_ID - info o filmie
POST http://localhost:8090/api/v3/add/string:oauth_ID/string:username - dodawanie usera
POST http://localhost:8090/api/v3/add/string:oauth_ID/string:movie_ID/int:rating - dodawanie oceny do filmu przez usera
GET http://localhost:8090/api/v3/ai/string:oauth_ID - wyciąganie rekomendacji od AI