How candyvelazco100/flower_shop_app works
Project type and purpose
• This is a full-stack web application (“Flora Vibrante”) for managing sales, purchases, users, products and receipts in a flower shop.
• It consists of a Python/Flask backend (in source/) and a Node.js-based SOAP microservice (in webservice/), all wired together via Docker Compose and persisting data in a MySQL database.
File structure
• Top‐level directories:
• source/ – main Flask service, organized by controllers (app.py, app_rest.py), models (models/), static assets (static/), templates (templates/), and a separate client subfolder (source/client/) hosting a JS-driven UI with Handlebars and plain JS.
• webservice/ – a standalone Node.js app exposing SOAP endpoints (soap_service.py in Python wrapper, plus index.js, app.js) to integrate with external systems.
• database/ – MySQL schemas, init scripts and dumps.
• Docker support: Dockerfile, docker-compose.yaml.
• Architectural cues:
• MVC pattern in Flask (models/, templates/, route handlers).
• Clear separation of concerns: backend API vs. client UI vs. microservice.
README
• Confirms: Flask + MySQL + Node.js SOAP.
• Describes the database schema, entity models, and high-level feature set (users, products, receipts, etc.).
• Outlines environment setup and Docker deployment.
Essential detail checklist
• MVC layers inside Flask (Controllers, Models, Views).
• Both the web UI routes and REST endpoints.
• Do not omit the Node.js SOAP microservice—treat it as a first-class component.
• Data flow from the user’s browser all the way to persistent storage.