How sunn4es/bsuir works
This is a collection of independent university coursework projects, not one integrated application. The sampled code supports several distinct workflows: file operations over HTTP, bank transactions, task management, proxy forwarding, and compiler exercises. The tree also contains many algorithm and desktop assignments, but the excerpts do not establish a shared runtime or wiring between them. Some bank dependencies are visible only as imports/calls, so their source paths are left null; other unsampled subsystem links are omitted.
Main entry points: bankController.js Bank controller · server.js Task API · Program.cs HTTP proxy · main.c Literal checker
Components 23
File Services
- REST routes
4 semester/Coputer Systems and Networks/REST_API/REST_API/Program.cs - File operations
4 semester/Coputer Systems and Networks/REST_API/REST_API/FileStorage/FileStorage.cs - Local filesystem
Bank Backend
- Bank controller
7 semester/PISm/Project/backend/src/controllers/bankController.js - Database pool
- Ledger service
- Credit schedule
- Bank database
Task Service
- Task API
7 semester/SPP/lab2_3/server/server.js - Auth middleware
7 semester/SPP/lab2_3/server/server.js - In-memory tasks/users
7 semester/SPP/lab2_3/server/server.js - Static client
Network Tools
- HTTP proxy
4 semester/Coputer Systems and Networks/ProxyServer/ProxyServer/Program.cs
Compiler Exercises
- Literal checker
3 semester/Compiler Technologies/Lab1/Project/main.c - Text input
- Token parser
3 semester/Compiler Technologies/Lab3/main.c - Token file
Other components
- API client
- Bank operator
- Web user
- Proxy client
- Origin server
- Compiler exercise user
Connections 22
- API client → REST routes: sends requests
- REST routes → File operations: dispatches operations
- File operations → Local filesystem: reads and writes
- Bank operator → Bank controller: requests bank actions
- Bank controller → Database pool: queries and transacts
- Bank controller → Ledger service: posts entries
- Bank controller → Credit schedule: computes schedule
- Database pool → Bank database: accesses
- Web user → Task API: uses task API
- Task API → Auth middleware: guards task routes
- Task API → In-memory tasks/users: reads and updates
- Task API → Static client: serves static files
- Proxy client → HTTP proxy: sends HTTP request
- HTTP proxy → Origin server: forwards request
- Origin server → HTTP proxy: returns response
- HTTP proxy → Proxy client: relays response
- Compiler exercise user → Literal checker: provides input
- Literal checker → Text input: reads or prompts
- Literal checker → Compiler exercise user: prints validation or literals
- Token parser → Token file: reads tokens
- Compiler exercise user → Token parser: runs parser
- Token parser → Compiler exercise user: prints accept or reject