A versioned Web API with a real MVC client.
An end-to-end ASP.NET Core project covering API design, authentication, PostgreSQL persistence, a Razor client, documentation, containers, and VPS deployment.
Designed for reviewers who want the purpose, ownership, and technical depth without digging through the repository first.
RoyalVilla manages villas and amenities through REST endpoints. A separate MVC application consumes those endpoints, so the API is exercised by a real client rather than existing only as an OpenAPI demo.
My scope covered the API, shared contracts, data access, authentication flow, MVC integration, container setup, health checks, documentation, and deployment.
The MVC client and API share DTO contracts but remain independently deployable applications.
MVC controllers and Razor views call the API through a named HttpClient. Browser sessions use cookie authentication.
Versioned controllers own CRUD behavior, JWT issuance, mapping, response envelopes, and OpenAPI documents.
Shared request and response types keep both apps aligned; EF Core handles persistence, relationships, seed data, and migrations.
A Razor page sends the request to an MVC controller.
The service calls /api/v1/villa and forwards the session JWT as a Bearer token.
The controller queries PostgreSQL asynchronously through EF Core.
AutoMapper creates a DTO, wrapped in ApiResponse<T>, for the Razor view.
A concise view of the backend, client integration, data layer, and delivery work represented in the repository.
Villa and amenity resources use typed inputs, appropriate status codes, async handlers, and a consistent response envelope.
URL-based v1 and v2 routing generates separate OpenAPI documents and demonstrates API evolution.
The API issues claims in a JWT; the MVC app signs users into a cookie session and forwards the token to API calls.
Entity relationships, seed data, migrations, and asynchronous queries are isolated behind the API boundary.
Request models, response models, and ApiResponse<T> are shared without exposing persistence entities to the client.
Multi-stage images, Compose networks, persistent volumes, health checks, HTTPS domains, and Dokploy support the live deployment.
Use the MVC application for the user flow or Scalar to inspect endpoints, schemas, and example requests.
Responsive Razor views backed entirely by API calls.
Versioned endpoints, schemas, authentication, and request examples.
Each tool has a specific place in the request path or delivery workflow.
RoyalVilla is an educational engineering project, not a commercial booking platform. The following limitations are intentional and documented; a production version would address them before release.
PasswordHasher<TUser> or BCrypt.Customer role instead of accepting Admin from the request.