How ttnghia-vaino/gomsu works
Project type and purpose
• The file tree and minimal README indicate “GomSu” is an ASP.NET Core MVC web application—likely an e-commerce site for pottery/ceramics (“SanPham”, “DonHang”, “GioHang” models).
• It follows the typical MVC pattern with Controllers, Models, Views, data access via Entity Framework Core (GomsuContext), and an email service.
File structure
• Top-level:
• GomSu/Controllers — MVC controllers (Account, Home, SanPham)
• GomSu/Models — EF Core entities + DbContext + other domain models (Order, Product, Cart, Voucher, EmailSettings)
• GomSu/Services — application services (EmailService)
• GomSu/ViewModels — DTOs for forms (Register, Login, ForgotPassword)
• GomSu/Views — Razor views and partials for each controller + shared layout
• wwwroot — static assets (css, js, images, libs)
• appsettings.json & appsettings.Development.json — configuration (database connection, SMTP)
• Program.cs & launchSettings.json — ASP.NET Core startup and environment config
README for additional insights
• README contains only project title. No explicit architecture notes, so we infer from structure and naming.
Elements
• Clear labels: “Browser,” “ASP.NET Core MVC App,” “SQL Database,” “SMTP Server”
• Browser → Controller (HTTP requests)
• Controller → DbContext → Database (data flow)
• Controller/Service → SMTP (email sending)
• Another for server-side code (Controllers, Services, Models)
• Another for external systems (Database, SMTP)