How wisenheim/python--instrumarket works
Project type and purpose
• Key indicators: a “static” folder (CSS, images), “templates” folder (HTML views), a controller.py (routing/business logic), Model and DM_PG modules (domain and data‐access layers), plus database scripts.
File structure
• Top-level directories:
• DM_PG – data‐manager module (DM.py) responsible for direct database operations.
• Model – domain model classes and business entities (Model.py).
• Database – SQL scripts to create/drop/populate the PostgreSQL (or similar) database.
• UnitTest – automated tests calling uTests.py to validate functionality.
• static – frontend assets (CSS frameworks, theme files, images).
• templates – Jinja2 or similar HTML templates (catalogo.html, index.html, login.html, strumenti.html).
• Top-level files:
• controller.py – central request handler (likely a Flask app).
• README.md, InstruMarket.pdf, TestList.pdf – documentation.
• No separate “frontend” folder, but static+templates serve that role. No microservices; it’s a monolith.