How aungsett/git_2026internship_team_c works
What this project is (type + purpose) inferred from the repo
Even though the root README.md is empty besides “Team C”, the file tree is very indicative:
• Full-stack web application with:
• Backend: Python web service in backend/app with extensions.py, config.py, run.py, seed.py, and Alembic migrations under backend/migrations. This strongly suggests Flask + SQLAlchemy (+ Flask-Migrate/Alembic) style architecture.
• Frontend: Next.js (App Router) in frontend/app with layout.tsx, page.tsx, Tailwind (tailwind.config.ts, globals.css) and Next config.
• Domain model (from backend/app/models/):
• admin.py, applicant.py, document.py, review.py
• That reads like an application intake + document submission + review workflow system (admin reviews applicants and documents, creates reviews, etc.).
Backend (Python service)
Key items to map:
• backend/run.py: entrypoint (HTTP server start)
• backend/app/__init__.py: Flask app factory / initialization (where routes/blueprints likely get registered even if not shown here)
• backend/app/extensions.py: shared infrastructure wiring, typically:
• SQLAlchemy instance
• Migration tool
• Possibly CORS, login/auth, etc.
• backend/app/models/*: data layer / ORM models
• backend/migrations/*: schema management (Alembic)
• backend/seed.py: data seeding / bootstrap
• backend/config.py: configuration (env-based settings: DB URL, secrets, debug)
• backend/requirements.txt: runtime dependencies
Frontend (Next.js)
Key items to map:
• frontend/app/layout.tsx: top-level layout (shell)
• frontend/app/page.tsx: initial route/page
• frontend/app/globals.css + Tailwind config: styling pipeline
• frontend/package.json: build scripts + dependencies
Frontend Container: Next.js
• Node.js runtime
• Renders UI, hosts routes from frontend/app/*
• Uses Tailwind build pipeline
Backend Container: Flask API
• Python runtime
• App initialization (app/__init__.py)
• Infrastructure (extensions.py)
• ORM models (models/*.py)
• Config (config.py)
Database Container: Relational DB
• Schema managed by Alembic migrations (migrations/*)
• Seed data via seed.py
Connections (label with protocol + payload):
• Browser → Next.js: HTTP(S) (HTML/CSS/JS)
• Next.js → Flask API: HTTP(S) JSON (REST-like)
• Flask API → DB: SQL via SQLAlchemy
• Dev/CI → Alembic migrations → DB (schema updates)
• Dev/CI → seed.py → DB (initial data)
• App Initialization
• app/__init__.py
• Extensions / Infrastructure
• app/extensions.py (SQLAlchemy, migration binding, etc.)
• Domain Model (ORM)
• models/admin.py
• models/applicant.py
• models/document.py
• models/review.py
• Schema Management
• migrations/ (Alembic)
• Bootstrap
• seed.py
Architectural patterns that are evident from the repo
• Separation of concerns by repo structure:
• frontend/ and backend/ are independent build/deploy units
• ORM-driven persistence:
• models/ + Alembic migrations indicates a relational DB with versioned schema
• “Extensions” pattern in Flask:
• central place (extensions.py) for DB/migrations integration
• Config-by-environment:
• config.py implies environment-specific settings; show “Environment variables / Config” feeding backend (and optionally frontend)