How anktuan/qlt works
Project type and purpose
• This is a full-stack pharmacy management system (“pharmacy-management/quanlythuoc”) composed of a React frontend and a Django REST-API backend.
• Purpose: allow employees and customers to register/login, manage medicines catalog, handle sales orders, payments, invoices, and integrate a chatbot.
File structure
• Top-level directories:
• backend/ – Django project (“pharmacy”) and three Django apps: authentication, medicines, sales, plus fixtures and media storage.
• frontend/ – React application, includes pages (Accounts, Customers, Dashboard, etc.), shared components, services (chatbotService), and configuration.
• docs/ – API documentation for each subsystem (auth_api.md, medicines_api.md, sales_api.md, swagger_api.md).
• Key files:
• backend/pharmacy/settings.py, urls.py, wsgi.py, asgi.py – project configuration.
• backend/*/views.py, serializers.py, urls.py – REST API endpoints via Django REST Framework.
• frontend/src/services/chatbotService.js & backend/pharmacy/chatbot_service.py – chatbot integration.
• fixtures/ – initial data for DB.
• media/ – uploaded medicine images.
• requirements.txt / package.json – dependencies.
README
• Limited description, but naming conventions confirm “pharmacy management.”
• No explicit architecture section, so infer stack: React + DRF + relational DB.
Essential details to capture
• All three Django apps and their respective database tables.
• The React pages and major components (Chatbot, Header/Footer, Dashboard).
• The chat-bot integration path.
• The API documentation endpoint (Swagger).
• Data flow for user auth, CRUD on medicines, order processing, payment, invoice generation.