How sergioizq/gastosapp-backend works
Project type and purpose
• This solution (“AppG.sln”) contains three .NET-based components plus a Dockerfile:
• AppG: a .NET Core Web API that exposes a RESTful service for personal/professional expense management
• CronJobProgramado: a .NET Core console job that runs on a schedule to process “GastoProgramado” (scheduled expenses)
• NHTools: a Windows Forms desktop utility that uses NHibernate mappings against the same database
• The README confirms AppG is the backend for a personal finance frontend, exposing endpoints for ingresos, gastos, cuentas, categorías, conceptos, personas, clientes, proveedores, traspasos and a financial summary.
File structure
• Top level:
• AppG/ – API project: Controllers, Servicio (service layer), BBDD (domain & NHibernate mappings), Middleware, Exceptions, NHibernate config, Startup & Program
• CronJobProgramado/ – scheduled job: NHibernate helper, job class, config
• NHTools/ – WinForms app: Form1, NHibernate config, binaries
• Dockerfile – to containerize the API (likely AppG)
• Patterns: Layered architecture in AppG: Controller → Service interfaces & implementations → NHibernate ORM → PostgreSQL (Supabase).
CronJobProgramado follows a similar layer but focuses on scheduled tasks.
NHTools is a standalone NHibernate client.
README for additional insights
• Stack: Nginx + VPS, .NET Core API, Supabase (PostgreSQL), JWT for auth, Swagger for docs, CORS enabled.
Detail
• Call out external dependencies (Supabase, Nginx on VPS) explicitly.