How team-3-softserve-academy/tournamenthall works
TournamentHall is presented as a tournament-themed web application, but the README documents no detailed tournament features. The sampled Flask app supports a basic login form, session assignment, redirect to a knights-book route, and placeholder registration/logout routes. Separate SQLAlchemy models and role repositories define persistence, but the sampled app does not connect them to its routes. The runtime picture is therefore limited to demonstrated behavior; database wiring beyond the model/repository references is not inferred.
Main entry points: models.py Domain models · run.py Flask routes · user_repository.py User repository · knight_repository.py Knight repository
Components 10
Web application
- Flask routes
app/run.py - Login view
app/templates/login.html - Base view
app/templates/base.html
Persistence
- Domain models
database/models.py - User repository
database/repositories/user_repository.py - Knight repository
database/repositories/knight_repository.py - Lord repository
database/repositories/lord_repository.py - Common folk repository
database/repositories/common_folk_repository.py
Other components
- Visitor
- PostgreSQL
Connections 8
- Visitor → Flask routes: submits login
app/run.py - Flask routes → Login view: renders login
app/run.py - Flask routes → Base view: renders page
app/run.py - Domain models → PostgreSQL: creates tables
database/models.py - User repository → Domain models: queries models
database/repositories/user_repository.py - Knight repository → Domain models: creates and queries
database/repositories/knight_repository.py - Lord repository → Domain models: creates and queries
database/repositories/lord_repository.py - Common folk repository → Domain models: creates and queries
database/repositories/common_folk_repository.py