This is a minimalist, non-layered startup solution with the ABP Framework. All the fundamental ABP modules are already installed.
@ -15,7 +15,7 @@ The solution comes with a default configuration that works out of the box. Howev
* Check the `ConnectionStrings` in `appsettings.json` files under the `MyCompanyName.MyProjectName` project and change it if you need.
### Preparings for the first run
### Before running the 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.
* The application needs to connect to a database. Run the following command in the `MyCompanyName.MyProjectName` directory:
@ -26,7 +26,7 @@ dotnet run --migrate-database
This will create and seed the initial database. Then you can run the application with any IDE that supports .NET.
## Deploying the Application
## 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](https://docs.abp.io/en/abp/latest/Deployment/Index) before deploying your application.
@ -35,3 +35,35 @@ Deploying an ABP application is not different than deploying any .NET or ASP.NET
You can see the following resources to learn more about your solution and the ABP Framework:
This is a layered startup solution based on [Domain Driven Design (DDD)](https://docs.abp.io/en/abp/latest/Domain-Driven-Design) practises. All the fundamental ABP modules are already installed.
@ -34,7 +34,7 @@ The solution comes with a default configuration that works out of the box. Howev
</TEMPLATE-REMOVE>
</TEMPLATE-REMOVE>
### Preparings for the first run
### Before running the 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 `MyCompanyName.MyProjectName.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.
@ -77,7 +77,7 @@ This is a layered monolith application that consists of the following applicatio
</TEMPLATE-REMOVE>
</TEMPLATE-REMOVE>
## Deploying the Application
## 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](https://docs.abp.io/en/abp/latest/Deployment/Index) before deploying your application.
@ -87,3 +87,35 @@ You can see the following resources to learn more about your solution and the AB
* [Web Application Development Tutorial](https://docs.abp.io/en/abp/latest/Tutorials/Part-1)