How danielleiva1/tareasitu works
Project type and purpose
• This is a full-stack web application built on the Django framework.
• It serves HTML pages (templates) with dynamic data stored in a SQLite database, packaged via Docker.
File structure
• Top level
• Dockerfile – builds a container image for the app
• manage.py – Django’s command-line utility
• requirements.txt – Python dependencies
• sonar-project.properties – code-analysis configuration
• db.sqlite3 – the embedded database file
• ProyectoSITU/ProyectoSITU
• settings.py, urls.py, wsgi.py, asgi.py – Django project configuration & entrypoints
• ProyectoSITU/appSITUweb
• models.py – data schema
• views.py, forms.py – request handling and form definitions
• admin.py – Django admin integration
• migrations/ – database schema history
• tests.py, test_models.py – unit tests
• templates/ – Jinja-style HTML templates (base.html, index.html, etc.)
• templates/static – CSS and other static assets
README
• The README only includes a title (“TareaSitu”), so all architectural insight comes from the structure above.
Main components and interactions
a. Components
1. Client (Browser)
2. Docker container
• Nginx (optional reverse-proxy) or direct Gunicorn/ASGI server
• Django application
3. Django subsystems
• URL Dispatcher (urls.py)
• View layer (views.py, forms.py)
• Model layer (models.py + migrations)
• Template Engine (templates/)
4. Database (SQLite – db.sqlite3)
5. Static files server (templates/static)
6. CI/Code analysis (SonarQube via sonar-project.properties)
b. Relationships & data flow
• Browser → HTTP request → (Nginx/gunicorn) → Django URL dispatcher
• URL dispatcher → appropriate view → may use forms for input validation
• View → ORM → SQLite database → returns QuerySet or object
• View → Template Engine → HTML response → Browser
• Static assets requested → static file handler
• Tests & migrations are developer operations, invoked via manage.py
c. Architectural patterns
• Monolithic MVC (Model-View-Template) layered structure within Django
• Containerized deployment with Dockerfile
• Optional code-quality gate via SonarQube
d. Key technologies
• Python 3.x, Django
• SQLite (development) – could be swapped for Postgres in production
• Docker
• (Optional) Gunicorn or Uvicorn for ASGI
• HTML/CSS templates