How colertrash1721/netolocker works
Project type and purpose
• This is a full-stack web application (“Seal Request and Tracking System”) for ESC-GROUP.
• Frontend: Next.js + Tailwind CSS for user interfaces (seal request form, real-time tracking, admin panel).
• Backend: NestJS REST (and potentially WebSocket) API for business logic, user/auth management, request processing.
• Infrastructure: Docker containers orchestrated via Docker-Compose, with NGINX as a reverse proxy.
(implied) file structure
Even though only README.md is listed, the README implies a typical layout:
• docker-compose.yml & .env (root)
• /frontend (Next.js + Tailwind)
• /backend (NestJS app)
• /nginx (NGINX config files, e.g. default.conf)
• /shared or /common (env files, utility scripts)
• .dockerignore, Dockerfile.frontend, Dockerfile.backend
README for additional insights
• Features: user roles (admin vs. regular), real-time location tracking, request forms, admin dashboard.
• Tech stack: Next.js, Tailwind CSS, NestJS, Docker, NGINX.
• Deployment: “docker-compose up --build” suggests multi-container setup with reverse proxy.
Final recommendations
– Capture all containers and their networking via Docker-Compose.
– Show module-level components inside NestJS (e.g., AuthModule, RequestModule).
– In the Frontend, illustrate pages/components for RequestForm, TrackingDashboard, AdminPanel.