@@ -29,27 +29,32 @@ In real world scenarios you can replace the web server and the blob storage with
29
29
az signalr create --resource-group <resource_group_name> --name <signalr_name> --sku Standard_S1
30
30
```
31
31
32
- 1. Create a web app using [ Azure CLI].
32
+ 1. Create a web app using Azure CLI:
33
33
34
34
```
35
35
az appservice plan create --name <plan_name> --resource-group <resource_group_name> --sku S1 --is-linux
36
36
az webapp create \
37
37
--resource-group <resource_group_name> --plan <plan_name> --name <app_name> \
38
- --runtime "dotnetcore|2 .1"
38
+ --runtime "dotnetcore|3 .1"
39
39
```
40
40
41
41
1. Deploy flight map to web app:
42
42
43
- ```
44
- az webapp deployment source config-local-git --resource-group <resource_group_name> --name <app_name>
45
- az webapp deployment user set --user-name <user_name> --password <password>
46
-
47
- git init
48
- git remote add origin <deploy_git_url>
49
- git add -A
50
- git commit -m "init commit"
51
- git push origin master
52
- ```
43
+ a. Publish the app
44
+ ```
45
+ dotnet publish -c Release
46
+ ```
47
+
48
+ b. Package the published app into a zip file (or use whatever zip tool you like to do it)
49
+ ```
50
+ cd bin/Release/netcoreapp3.1/publish
51
+ zip app.zip * -r
52
+ ```
53
+
54
+ c. Publish using Azure CLI
55
+ ```
56
+ az webapp deployment source config-zip -n <app_name> -g <resource_group_name> --src app.zip
57
+ ```
53
58
54
59
1. Prepare flight data
55
60
@@ -80,7 +85,6 @@ In real world scenarios you can replace the web server and the blob storage with
80
85
1. Update settings of web app:
81
86
82
87
```
83
- az webapp config appsettings set --resource-group <resource_group_name> --name <app_name> --setting PORT=5000
84
88
az webapp config appsettings set --resource-group <resource_group_name> --name <app_name> \
85
89
--setting Azure__SignalR__ConnectionString=<connection_string>
86
90
az webapp config appsettings set --resource-group <resource_group_name> --name <app_name> \
0 commit comments