LQ.Microservice

About this solution

This is a layered startup solution based on Domain Driven Design (DDD) practises. All the fundamental ABP modules are already installed.

Pre-requirements

• .NET 8.0+ SDK
• Node v18 or 20
• Redis

Configurations

The solution comes with a default configuration that works out of the box. However, you may consider to change the following configuration before running your solution:

• Check the ConnectionStrings in appsettings.json files under the LQ.Microservice.AuthServer, LQ.Microservice.HttpApi.Host and LQ.Microservice.DbMigrator projects and change it if you need.

Before running the application

Generating a Signing Certificate

In the production environment, you need to use a production signing certificate. ABP Framework sets up signing and encryption certificates in your application and expects an openiddict.pfx file in your application.

This certificate is already generated by ABP CLI, so most of the time you don't need to generate it yourself. However, if you need to generate a certificate, you can use the following command:

dotnet dev-certs https -v -ep openiddict.pfx -p ae328f32-0e31-445e-af20-84f8781c3a5e

ae328f32-0e31-445e-af20-84f8781c3a5e is the password of the certificate, you can change it to any password you want.

It is recommended to use two RSA certificates, distinct from the certificate(s) used for HTTPS: one for encryption, one for signing.

For more information, please refer to: https://documentation.openiddict.com/configuration/encryption-and-signing-credentials.html#registering-a-certificate-recommended-for-production-ready-scenarios

Also, see the Configuring OpenIddict documentation for more information.

Install Client-Side Libraries

Run the following command in the directory of your final application:

abp install-libs

This command installs all NPM packages for MVC/Razor Pages and Blazor Server UIs and this command is already run by the ABP CLI, so most of the time you don't need to run this command manually.

Deploying the Application

Deploying an ABP application is not different than deploying any .NET or ASP.NET Core application. However, there are some topics that you should care about when you are deploying your applications. You can check ABP's Deployment documentation before deploying your application.

• Run abp install-libs command on your solution folder to install client-side package dependencies. This step is automatically done when you create a new solution with ABP CLI. However, you should run it yourself if you have first cloned this solution from your source control, or added a new client-side package dependency to your solution.
• Run LQ.Microservice.DbMigrator to create the initial database. This should be done in the first run. It is also needed if a new database migration is added to the solution later.

Solution structure

This is a layered monolith application that consists of the following applications:

• LQ.Microservice.DbMigrator: A console application which applies the migrations and also seeds the initial data. It is useful on development as well as on production environment.
• LQ.Microservice.AuthServer: ASP.NET Core MVC / Razor Pages application that is integrated OAuth 2.0(OpenIddict) and account modules. It is used to authenticate users and issue tokens.
• LQ.Microservice.HttpApi.Host: ASP.NET Core API application that is used to expose the APIs to the clients.
• LQ.Microservice.Web: ASP.NET Core MVC / Razor Pages application that is the essential web application of the solution.

Deploying the application

Deploying an ABP application is not different than deploying any .NET or ASP.NET Core application. However, there are some topics that you should care about when you are deploying your applications. You can check ABP's Deployment documentation before deploying your application.

Additional resources

You can see the following resources to learn more about your solution and the ABP Framework:

• Web Application Development Tutorial
• Application Startup Template Structure
• LeptonX Lite MVC UI