Azure App Services
Deploy DasBlog Core to Azure App Services for Linux or Windows. For other deployment options see the Deployment page.
- Publish: Code
- Runtime Stack: .NET 10
- Operating System: Linux
- SKU & size: B1 or above is recommended for production use.
Download the latest version of the DasBlog Core zip files. To upload the content of the zip file you will need to grab your FTP credentials from Deployment Center in the Azure Portal and upload the files to the site root location (site/wwwroot) using an FTP client.
Go to your App Service in the Azure Portal and navigate to Configuration settings and under Application Settings click the New Application Setting button to create a new setting with the following name and value:
- Name: ASPNETCORE_ENVIRONMENT
- Value: Production
Under General Settings ensure the the Stack Settings are as follows:
- Stack: .NET
- Major Version: .NET 10
- Startup Command: dotnet DasBlog.Web.dll
Go to your App Service in the Azure Portal click on the Advanced Tools then click on SSH. At the prompt type the following commands to configure DasBlog Core with your sites root URL.
cd ..
cd home\site\wwwroot
dotnet dasblog-core.dll init
dotnet dasblog-core.dll config root https://yoursitename.azurewebsites.net
- Publish: Code
- Runtime Stack: .NET 10
- Operating System: Windows
- SKU & size: B1 or above is recommended for production use.
Download the latest version of the DasBlog Core zip files. To upload the content of the zip file you will need to grab your FTP credentials from Deployment Center in the Azure Portal and upload the files to the site root location (site/wwwroot) using an FTP client.
Go to your App Service in the Azure Portal and navigate to Configuration settings and under Application Settings click the New Application Setting button to create a new setting with the following name and value:
- Name: ASPNETCORE_ENVIRONMENT
- Value: Production
Under General Settings ensure the the Stack Settings are as follows:
- Stack: .NET
- .NET Version: .NET 10
Go to your App Service in the Azure Portal and click on the Advanced Tools then click on Debug Console->CMD. At the prompt type the following commands to configure DasBlog Core with your sites root URL.
cd site\wwwroot
dasblog-core init
dasblog-core config root https://yoursitename.azurewebsites.net
This is the scenario where your blog is a part of a larger site and you choose to deploy dasblog-core as a 'subfolder'. The site.config will look similar to this <root>https://yourdomain.com/{blog}</root>. The exact subfolder structure is up to you and dasblog-core supports whatever path you choose.
When you deploy in this manner to Azure you will create a subdirectory virtual application for your blog on the site. Depending on what OS you host on and on what platform, it may look different, but here is what this looks like on Azure App Services for Windows:
The /blog virtual path is mapped to the site\wwwblog physical folder. You deploy dasblog-core to that folder.
The deployment of files into this folder is supported directly in MS Deploy Web Publish. You configure the deployment to send the files to a certain path on your site and the IIS will save the files to the physical folder configured as the target for the virtual application.
This is what that looks like in Visual Studio in the publish file:
If you follow this approach your blog will be an aspect of your site and you can deploy it in exactly the same manner as the rest of your site. The approach has clear advantages and an additional responsibility. You will need to synchronize styling and menu options between the two sites / and /blog, but the advantage is that you get a site-integrated blog feature and can also host other content on the same site.
If you have additional questions or concerns please submit an issue.