This is a minimalist, non-layered startup solution with the ABP Framework. 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 theAcme.TestAbpproject and change it if you need.
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 e0689e94-0c9a-4e23-88b9-8975b5756a25
e0689e94-0c9a-4e23-88b9-8975b5756a25is 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.
Run the following command in the directory of your final application:
abp install-libsThis 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.
The application needs to connect to a database. Run the following command in the Acme.TestAbp directory to migrate the database and seed the initial data:
dotnet run --migrate-databaseThis command will create and seed the initial database. Then you can run the application with any IDE that supports .NET.
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: