How aeternum-web/sistema-fime works
Project type and purpose
• Sistema FIME is a full-stack, community-driven web application built with .NET/Blazor for the Facultad de Ingeniería Mecánica y Eléctrica (FIME) student community.
• Purpose: enable student communication, Q&A, sharing experiences, and collaborative features via a modern SPA.
File structure
• Top-level “SistemaFIME” folder houses the Blazor project:
• Pages/ & Pages/Shared: client UI components (Razor pages, layouts, shared menus, content sections).
• Data/ApplicationDbContext.cs: EF Core data layer.
• Models: domain DTOs (DashboardModels.cs).
• wwwroot: static assets (CSS, JS) including Tailwind setup.
• Dockerfile(.dev), docker-compose.yml/dev, .env, build/test scripts: containerization and local orchestration.
• Node modules, package.json, tailwind.config.js, build-tailwind.sh: front-end styling toolchain.
• Program.cs, App.razor, _Host.cshtml: application startup and hosting.
README for additional insights
• Tech stack: C#, .NET (Blazor), PostgreSQL.
• Deployment via Docker.
• No external third-party services beyond a relational database.
Main components
a. Presentation Layer
• Blazor SPA running in the browser.
• Entry point: App.razor → Router → Pages/*.razor.
• Shared UI components under Pages/Shared (menus, layouts, cards).
b. Business Logic Layer
• Razor page code-behind or injected services (if present).
• Feature components (e.g., DashboardModels) orchestrate data fetch & UI rendering.
c. Data Access Layer
• ApplicationDbContext (EF Core) connecting to PostgreSQL.
• Models folder defines the schema for dashboards, comments, materias, profesores.
d. Infrastructure & Deployment
• Docker image (Dockerfile) with ASP.NET host.
• docker-compose for local dev: services for web app and postgres.
• build-tailwind.sh & Node toolchain generate CSS assets pre-deployment.
e. External Services
• PostgreSQL container or managed service.
• (Optionally) future integrations: email, authentication providers (not in current tree).
Relationships and interactions
• Browser ←→ Blazor WebAssembly or Blazor Server (hosted) over HTTP.
• Web host (Kestrel) processes Razor pages, serves static wwwroot content.
• EF Core inside web host issues SQL queries to PostgreSQL.
• build/test scripts run on the CI/dev workstation, produce Docker images, push to registry or deploy.
Architectural patterns & design principles
• Layered architecture (Presentation → Business → Data).
• Component-based UI with reusable Razor components.
• Containerization (micro-VM per service) for reproducible environments.
• Modular CSS with Tailwind to keep styling consistent.
Detail
• That the EF Core ApplicationDbContext → PostgreSQL link is explicit.
• DevOps scripts (docker-compose, build-tailwind, start.sh) to show how the system comes up end-to-end.