How sanima2025/sanima-fichas works
Project type and purpose
• This is a single‐page web application built with Streamlit (a Python web‐app framework) as indicated by the presence of app.py and the .streamlit folder.
• The project name (“sanima-fichas”) suggests it renders or manages “fichas” (records/cards), but the architecture is that of a lightweight, data‐driven Streamlit dashboard.
File structure
• Top level:
• app.py – main Streamlit application entry point
• requirements.txt – Python dependencies (e.g., streamlit, pandas, etc.)
• README.md – basic project metadata
• Config directories:
• .streamlit/config.toml – Streamlit runtime configuration (port, theme, etc.)
• .devcontainer/ – VS Code Dev Container config for reproducible development environment
Extract insights from README
a. Main components to represent:
• User (web browser)
• Streamlit Server (runs app.py inside a Python environment)
• Application Logic (modules and functions within app.py)
• Data Layer – local files (CSV/JSON) or external data sources/APIs if used
• Development Environment (VS Code Dev Container)
b. Relationships and interactions:
• Browser ↔ HTTP(S) ↔ Streamlit Server
• Streamlit Server → Python business‐logic functions → Data Layer
• Developer → VS Code in Dev Container → runs “streamlit run app.py”
c. Architectural patterns / design principles:
• Single‐process, event‐driven web server (Streamlit)
• MVC‐like separation:
– View = Streamlit UI elements in app.py
– Controller = user‐interaction callbacks
– Model = data ingestion/manipulation functions
• Containerized dev environment for reproducibility
d. Key technologies / libraries:
• Python 3.x
• Streamlit (UI + web server)
• Pandas / NumPy (common for data‐driven apps, check requirements.txt)
• VS Code Dev Container (Docker based)
Detail without over‐fragmentation
• Don’t break app.py into too many micro‐components unless it already has submodules.
• UI layer, application layer, data layer, and the dev environment boundary.