How mihatama/open-mes-project works
Project Type and Purpose
• This is a full-stack, containerized web application implementing an MES (Manufacturing Execution System).
• Frontend: React (Vite) single-page application with mobile/desktop views.
• Backend: Django + Django-REST Framework, organized into domain-specific apps (base, inventory, machine, master, production, quality, users).
• Infrastructure: Docker Compose orchestration, Nginx reverse proxies, Certbot for TLS, PostgreSQL database, utility scripts for test data.
File Structure
Top-level directories and their roles:
• backend/
• compose.yaml: orchestrates backend container
• image/: Dockerfile + Python requirements for Django service
• src/: Django project (“base” settings + multiple apps)
• frontend/
• Dockerfile(.prod): builds React app
• src/: React components, pages, layouts, utils
• index.html, package.json, nginx.conf: client served by Nginx
• db/
• compose.yaml + image/: builds PostgreSQL container
• reverse-proxy/, reverse-proxy_https/, reverse-proxy_prod/
• Dockerfiles + nginx.conf: front door for routing/SSL termination
• certbot/: builds container to obtain/renew TLS certs
• compose.yml(.prod/.https): root Docker Compose for all services
• docs/: architecture, tech-stack, API, developer guides
• script/: Python scripts for generating seed/test data
README for Additional Insights
• Confirms tech stack: Ubuntu, Docker, Docker Compose, PostgreSQL, Python 3.11.
• Describes environment setup, .env variables, migrations, superuser creation.
• Points to docs/ for deeper architecture and module descriptions.
Detailed but Focused
• How migrations (backend/src/*/migrations) interact with PostgreSQL.
• Path of static file serving: React build → Nginx → client.
• Environment config: .env, compose.yml, and how they tie components together.