How shubhamjha014/onit_clone works
Legal Management Portal is a Flask/PostgreSQL application for managing legal matters and related operational records. Users log in, then work through a live dashboard or the matter, invoice, contact, and task applications; matter records connect to budgets, allocations, participants, comments, activities, tasks, and invoices. Settings, reference lists, vendors, vendor assignments, and chatbot screens are additional registered capabilities. Routes render Jinja templates and read or write database records. The README and sampled source support the main workflows; several peripheral route implementations were not sampled, so their internal wiring is not inferred.
Main entry points: models Domain models · matters.py Matter management · __init__.py Flask app · invoices.py Invoices
Components 22
Access and UI
- Flask app
app/__init__.py - Authentication
app/routes/auth.py - Session auth
app/services/auth_service.py - Jinja screens
app/templates
Legal work
- Dashboard
app/routes/home.py - Matter management
app/routes/matters.py - Matter services
app/services/matter_service.py - Invoices
app/routes/invoices.py - Tasks
app/routes/tasks.py - Contacts
app/routes/contacts.py - Matter screens
app/templates/matters - Invoice screens
app/templates/invoices - Task screens
app/templates/tasks - Contact screens
app/templates/contacts
Operations
- Vendor records
app/routes/vendors.py - Matter assignments
app/routes/vatms.py - Administration
app/routes/settings.py - Reference lists
app/routes/lists.py - Chat interface
app/routes/chats.py
Persistence
- Domain models
app/models - PostgreSQL
Other components
- Portal user
Connections 31
- Portal user → Flask app: uses
- Flask app → Authentication: registers
- Flask app → Jinja screens: renders
- Authentication → Session auth: authenticates
- Session auth → Domain models: loads user
- Portal user → Dashboard: opens
- Portal user → Matter management: manages matters
- Portal user → Invoices: manages invoices
- Portal user → Tasks: manages tasks
- Portal user → Contacts: manages contacts
- Portal user → Vendor records: manages vendors
- Portal user → Matter assignments: manages assignments
- Portal user → Administration: administers
- Portal user → Reference lists: maintains lists
- Portal user → Chat interface: uses chat
- Dashboard → Domain models: queries live data
- Matter management → Matter services: uses numbering and logs
- Matter management → Domain models: reads and writes
- Invoices → Domain models: reads and writes
- Tasks → Domain models: reads and writes
- Contacts → Domain models: reads and writes
- Vendor records → Domain models: reads and writes
- Matter assignments → Domain models: reads and writes
- Administration → Domain models: reads and writes
- Reference lists → Domain models: reads and writes
- Matter services → Domain models: queries and records
- Domain models → PostgreSQL: persists records
- Matter management → Matter screens: renders
- Invoices → Invoice screens: renders
- Tasks → Task screens: renders
- Contacts → Contact screens: renders