How parkermedlin/kpk-app works
Project type and purpose
• This is a monolithic, full-stack Django web application (“Blendverse”) extended with auxiliary Python scripts for ETL, reporting, and local-machine utilities.
• Purpose: Replace spreadsheet/ERP interfaces in the chemical blending department with a unified web portal for MRP, inventory tracking, production analysis, safety checklists, and reporting.
File structure
• Top-level directories:
• app/ – Django project root, contains:
– app/ (project module: settings.py, asgi.py, wsgi.py, custom middleware, URL routing)
– core/, prodverse/, nav3d/, kpklauncher/ – separate Django “apps” each handling a feature domain
– templates/ and static assets under each app for frontend
– manage.py
• docker-compose-*.yml, Dockerfile, nginx/ – containerization and reverse-proxy configuration
• local_machine_scripts/ – standalone Python/batch/PowerShell scripts for data import, backups, ETL
• db_backups/, whls/ – artifacts and binary wheels
• Key patterns:
• MVC (Django’s MTV)
• Asynchronous tasks via Celery management commands
• WebSockets (Django Channels in core/consumers.py & ASGI)
• Static files served by NGINX (CSS/JS under each app’s static/)
• External integrations: Sage 100 via pyodbc, SMTP for emails, 3D viewer in nav3d
README for insights
• Primary modules live: forklift safety checklists, lot-number records, MRP updates, blend scheduling, issue-sheet generation
• Under-development modules: digital blend sheets, blend inventory counts
• Tech stack: Python 3.9, Django, Bootstrap 5, jQuery 3.6.0, PostgreSQL 13, pyodbc (Sage 100), Celery, Docker, NGINX
• On-premises deployment, uses CSV fallbacks