How akagamifr/secure-bank works
Secure Bank is a single-file banking web application: a user signs up or signs in, then uses an authenticated dashboard for account information and loan actions. The server embeds and serves the browser interface, handles API requests, and accesses PostgreSQL; multipart signup also accepts an identity image. The excerpt confirms loan history, cards, balance, and password-change interface elements, but omits their handlers and wiring, so those capabilities are not mapped as API flows.
Main entry points: server.js Banking interface · uploads Identity uploads
Components 9
Web interface
- Banking interface
server.js - HTTP server
server.js
Identity and access
- Signup and signin
server.js - JWT authentication
server.js
Banking services
- User profile
server.js - Loan actions
server.js
Other components
- Bank user
- PostgreSQL
- Identity uploads
uploads
Connections 13
- Bank user → Banking interface: uses
- Banking interface → HTTP server: requests pages
- HTTP server → Banking interface: serves interface
- Banking interface → Signup and signin: submits credentials
- Signup and signin → PostgreSQL: checks and stores users
- Signup and signin → JWT authentication: issues JWT
- Banking interface → User profile: requests profile
- User profile → JWT authentication: checks token
- User profile → PostgreSQL: reads user
- Banking interface → Loan actions: requests loan
- Loan actions → JWT authentication: checks token
- Loan actions → PostgreSQL: records loan and balance
- Signup and signin → Identity uploads: references uploaded image