How lancew/myjudo works
Main Components Identification
The system appears to be a web application with the following key components:
a. Web Server Layer
• Built with Cro (Perl 6 web framework)
• Handles HTTPS with TLS (evident from fake-tls certificates)
• Entry point through service.p6
b. Application Layer
• Routes handling (Routes.pm6)
• Core business logic (MyJudo.pm6, Judo.pm6)
• Template rendering (views directory with .mustache files)
c. Data Layer
• SQLite database (db/myjudo.db)
• Multiple schema versions showing evolution
[HTTPS/TLS Layer]
• ↓
[Cro Web Server]
• ↓
[Router (Routes.pm6)]
• ↓
[Application Logic]
• ↙ ↘
[Views] [Database]
Component Details
• Blue: External interfaces (HTTPS/TLS)
• Green: Application components (Cro, Router, Logic)
• Yellow: Data storage (SQLite)
• Orange: View layer (Mustache templates)
Key Relationships
• Request flow from HTTPS → Cro → Router → Logic
• Data flow between Logic ↔ Database
• Template rendering flow from Logic → Views
• Response flow back to client
Important Elements
a. Security Layer:
• TLS certificate handling
• Authentication flow (evident from login/register views)
b. Application Features:
• User management (register, login, password reset)
• Training session management
• User home functionality
c. Development/Deployment:
• Docker container support
• Development tools integration
Technical Details to Note
A technical stack sidebar:
• Language: Perl 6
• Web Framework: Cro
• Database: SQLite
• Template Engine: Mustache
• Container: Docker
• TLS: Self-signed certificates