dunk3nn/group_3

How dunk3nn/group_3 works

This is a border-entry administration system spanning an Express/MySQL API and PHP/MySQL screens, with browser JavaScript clients. Its core workflow manages travelers, vehicles, and entry records, then supports violations, alerts, fee rules, penalties, and payments; separate administration covers users, checkpoints, personnel, shifts, and assignments. The Node backend separates routing, controllers, models, and pooled database access, while several PHP screens access MySQL directly. The README documents major screens and reports; some unsampled integrations are therefore represented without asserting unverified call paths.

Main entry points: server.js Express API · db.php PHP Database Connection · entry_records.php Traveler And Vehicle Screens · db.js MySQL Pool

Components 28

API Runtime

Express API backend/server.js
MySQL Pool backend/config/db.js

Entry Operations

Entry Records backend/controllers/entryRecordController.js
Travelers backend/controllers/travelerController.js
Vehicles backend/controllers/vehicleController.js
Violations backend/controllers/violationController.js
Alerts backend/controllers/alertController.js
Audit Trail backend/models/auditLogModel.js
Entry Client frontend/js/entries.js

Fees And Payments

Fee And Payment API backend/server.js
Fee Rules php/kenn/fee_rules.php
Payments Client frontend/js/payments.js

Administration

User Management backend/controllers/userController.js
Personnel Management backend/controllers/personnelController.js
Shift Management backend/controllers/shiftController.js
Checkpoint Assignments backend/controllers/assignmentController.js
Checkpoint Data backend/routes/checkpointRoutes.js

PHP Screens

Traveler And Vehicle Screens php/divine/entry_records.php
Users And Roles php/albert/users.php
Personnel Screen personnel/index.php
Shift Screen shifts/index.php
Checkpoint And Lane Screens php/kyfer/lanes.php
Violations And Alerts php/michael/violations.php
Reports php/divine/entry_report.php
PHP Database Connection db.php

Other components

Staff User
Browser Clients frontend/js/api.js
MySQL Database

Connections 28

Staff User → Browser Clients: uses
Browser Clients → Express API: requests
Express API → Entry Records: routes backend/server.js
Express API → Travelers: routes backend/server.js
Express API → Vehicles: routes backend/server.js
Express API → Violations: routes backend/server.js
Express API → Alerts: routes backend/server.js
Express API → User Management: routes backend/server.js
Express API → Personnel Management: routes backend/server.js
Express API → Shift Management: routes backend/server.js
Express API → Checkpoint Assignments: routes backend/server.js
Express API → Checkpoint Data: routes backend/server.js
Express API → Fee And Payment API: serves backend/server.js
Violations → Audit Trail: writes backend/controllers/violationController.js
Alerts → Audit Trail: writes backend/controllers/alertController.js
Express API → MySQL Pool: queries backend/server.js
MySQL Pool → MySQL Database: connects backend/config/db.js
Fee Rules → PHP Database Connection: uses connection php/kenn/fee_rules.php
Traveler And Vehicle Screens → PHP Database Connection: uses connection php/divine/entry_records.php
Users And Roles → PHP Database Connection: uses connection php/albert/users.php
Personnel Screen → PHP Database Connection: uses connection personnel/index.php
Shift Screen → PHP Database Connection: uses connection shifts/index.php
Checkpoint And Lane Screens → PHP Database Connection: uses connection php/kyfer/lanes.php
Violations And Alerts → PHP Database Connection: uses connection php/michael/violations.php
PHP Database Connection → MySQL Database: connects db.php
Entry Client → Express API: requests
Payments Client → Express API: requests
Traveler And Vehicle Screens → Reports: supports reports

Drawn by GitDiagram on November 12, 2026 from the repository's file tree, README and source files. Read as Markdown ·