Architecture of wger-project/wger
wger-project/wger is 876 source files holding 4,910 symbols across 4 modules, written mainly in Python, Shell, Dockerfile. The largest module is wger, with 738 files, and 4 files are entry points into the dependency graph.
How wger fits together
Command-line tasks enter through manage.py, and the web application is served through the WSGI entry point in wger/wsgi.py. The settings directory builds Django configuration in layers, starting from the baseline in settings/settings_global.py. The wger directory holds most of the code, and wger/core provides the core identity and configuration behavior that other parts build on. API endpoints are implemented as views such as wger/core/api/views.py, and wger/measurements/api/serializers.py defines how measurement data is represented in the API. Records are stored through Django models, and Celery is listed as a dependency for background tasks.
Largest modules
- wger: 738 files and 66,572 lines of code
- extras: 11 files and 696 lines of code
- settings: 5 files and 857 lines of code
- root: 1 file and 6 lines of code
Languages
By file count: Python 742 files, Shell 6 files, Dockerfile 4 files, JavaScript 3 files.
Documentation
Repowise documents wger in 850 pages generated from the source, 52 of them written explanations of the repository and its modules. Module guides include:
- extras/authors: Author API and Fixtures
- wger/core/api: Core API Endpoints
- wger/core/management: Core CLI Commands
More on wger: summary and FAQ, codebase overview, code health.
Related guide: Best dependency graph tools for monorepos