This is a layered startup solution based on Domain Driven Design (DDD) practises. All the fundamental ABP modules are already installed.
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
ConnectionStringsinappsettings.jsonfiles under thecsuwf.PaperManagement.AuthServer,csuwf.PaperManagement.HttpApi.Hostandcsuwf.PaperManagement.DbMigratorprojects and change it if you need.
- Run
abp install-libscommand 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
csuwf.PaperManagement.DbMigratorto 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.
This is a layered monolith application that consists of the following applications:
csuwf.PaperManagement.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.csuwf.PaperManagement.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.csuwf.PaperManagement.HttpApi.Host: ASP.NET Core API application that is used to expose the APIs to the clients.angular: Angular 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.
You can see the following resources to learn more about your solution and the ABP Framework: