-
-
Notifications
You must be signed in to change notification settings - Fork 196
1. Deployment
- Choose your Azure Subscription
- Choose or create a Resource Group
- Choose a Region
- Choose A Unique Site Name
- SKU and Worker Size default to the recommended values for production
- Set the repo URL to your fork of DasBlog-Core (e.g. https://github.com/MYUSERNAME/dasblog-core.git)
- Choose the branch to deploy (main is recommended)
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
- Publish: Code
- Runtime Stack: .NET 6 (Early Access)
- 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 6
- Minor Version: .NET 6 (Early Access)
- 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 6 (Early Access)
- 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 6 (Early Access)
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 option requires a host that supports .NET 6.
Download the latest version of DasBlog Core zip files, unzip the content and open the DasBlog directory with a command line tool. Execute the following commands to configure your DasBlog configuration files:
dasblog-core.exe init
dasblog-core.exe config root https://www.yoursitename.com
Upload the updated content to your site root location, this can generally be accomplished with FTP (using an FTP client), or you can sign in an upload via the host provided user interface for managing files.
DasBlog Core requires sufficient permissions to read/write to its own directories specifically the Content and Config folders.
Download the latest version of DasBlog Core zip files, unzip the content and open the DasBlog directory with a command line tool. Execute the following commands to configure your DasBlog configuration files:
dasblog-core.exe init
dasblog-core.exe config root https://localhost:5001/
To run DasBlog locally run the following command from your preferred CLI:
DasBlog.Web.exe
Navigate to https://localhost:5001/
.
Note: You may see cert errors for connecting to localhost.
If you have additional questions or concerns please submit an issue.