Skip to content

Commit 4b423cd

Browse files
authored
Merge pull request #7210 from umbraco/azure-web-apps
Added updates to v15 and v16 as per v14 PR update
2 parents da681f7 + 5c12ad7 commit 4b423cd

File tree

3 files changed

+70
-5
lines changed

3 files changed

+70
-5
lines changed

14/umbraco-cms/fundamentals/setup/server-setup/load-balancing/azure-web-apps.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ The multi-instance Scalable Public Web App should be set to use [TempFileSystemD
3434
}
3535
}
3636
```
37+
3738
## Umbraco TEMP files
3839

3940
When an instance of Umbraco starts up it generates some 'temporary' files on disk. In a normal IIS environment, these would be created within the folders of the Web Application. In an Azure Web App, we want these to be created in the local storage of the actual server that Azure happens to be used for the Web App. So we set this configuration setting to 'true' and the temporary files will be located in the environment temporary folder. This is required for both the performance of the website as well as to prevent file locks from occurring due to the nature of Azure Web Apps shared files system.
@@ -50,7 +51,7 @@ When an instance of Umbraco starts up it generates some 'temporary' files on dis
5051
}
5152
```
5253

53-
#### Host synchronization
54+
### Host synchronization
5455

5556
Umbraco runs within a [.NET Host](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-6.0).
5657

15/umbraco-cms/fundamentals/setup/server-setup/load-balancing/azure-web-apps.md

Lines changed: 34 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,18 @@ The single instance Backoffice Administrative Web App should be set to use [Sync
2323

2424
The multi-instance Scalable Public Web App should be set to use [TempFileSystemDirectoryFactory](file-system-replication.md#examine-directory-factory-options).
2525

26+
```json
27+
{
28+
"Umbraco": {
29+
"CMS": {
30+
"Examine": {
31+
"LuceneDirectoryFactory" : "TempFileSystemDirectoryFactory"
32+
}
33+
}
34+
}
35+
}
36+
```
37+
2638
## Umbraco TEMP files
2739

2840
When an instance of Umbraco starts up it generates some 'temporary' files on disk. In a normal IIS environment, these would be created within the folders of the Web Application. In an Azure Web App, we want these to be created in the local storage of the actual server that Azure happens to be used for the Web App. So we set this configuration setting to 'true' and the temporary files will be located in the environment temporary folder. This is required for both the performance of the website as well as to prevent file locks from occurring due to the nature of Azure Web Apps shared files system.
@@ -39,7 +51,7 @@ When an instance of Umbraco starts up it generates some 'temporary' files on dis
3951
}
4052
```
4153

42-
#### Host synchronization
54+
### Host synchronization
4355

4456
Umbraco runs within a [.NET Host](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-6.0).
4557

@@ -63,7 +75,27 @@ By default **Umbraco v9.4 & 9.5** uses a system-wide semaphore locking mechanism
6375

6476
Apply this setting to both the **SCHEDULINGPUBLISHER** Administrative server and the **SUBSCRIBER** scalable public-facing servers.
6577

66-
## Steps to set-up an environment
78+
You can also copy the following JSON directly into your Azure Web App configuration via the Advanced Edit feature.
79+
80+
```json
81+
{
82+
"name": "UMBRACO__CMS__Global__MainDomLock",
83+
"value": "FileSystemMainDomLock",
84+
"slotSetting": false
85+
},
86+
{
87+
"name": "UMBRACO__CMS__Hosting__LocalTempStorageLocation",
88+
"value": "EnvironmentTemp",
89+
"slotSetting": false
90+
},
91+
{
92+
"name": "UMBRACO__CMS__Examine__LuceneDirectoryFactory",
93+
"value": "TempFileSystemDirectoryFactory",
94+
"slotSetting": false
95+
}
96+
```
97+
98+
## Steps to set up an environment
6799

68100
1. Create an Azure SQL database
69101
2. Install Umbraco on your backoffice administrative environment and ensure to use your Azure SQL Database

16/umbraco-cms/fundamentals/setup/server-setup/load-balancing/azure-web-apps.md

Lines changed: 34 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,18 @@ The single instance Backoffice Administrative Web App should be set to use [Sync
2323

2424
The multi-instance Scalable Public Web App should be set to use [TempFileSystemDirectoryFactory](file-system-replication.md#examine-directory-factory-options).
2525

26+
```json
27+
{
28+
"Umbraco": {
29+
"CMS": {
30+
"Examine": {
31+
"LuceneDirectoryFactory" : "TempFileSystemDirectoryFactory"
32+
}
33+
}
34+
}
35+
}
36+
```
37+
2638
## Umbraco TEMP files
2739

2840
When an instance of Umbraco starts up it generates some 'temporary' files on disk. In a normal IIS environment, these would be created within the folders of the Web Application. In an Azure Web App, we want these to be created in the local storage of the actual server that Azure happens to be used for the Web App. So we set this configuration setting to 'true' and the temporary files will be located in the environment temporary folder. This is required for both the performance of the website as well as to prevent file locks from occurring due to the nature of Azure Web Apps shared files system.
@@ -39,7 +51,7 @@ When an instance of Umbraco starts up it generates some 'temporary' files on dis
3951
}
4052
```
4153

42-
#### Host synchronization
54+
### Host synchronization
4355

4456
Umbraco runs within a [.NET Host](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-6.0).
4557

@@ -63,7 +75,27 @@ By default **Umbraco v9.4 & 9.5** uses a system-wide semaphore locking mechanism
6375

6476
Apply this setting to both the **SCHEDULINGPUBLISHER** Administrative server and the **SUBSCRIBER** scalable public-facing servers.
6577

66-
## Steps to set-up an environment
78+
You can also copy the following JSON directly into your Azure Web App configuration via the Advanced Edit feature.
79+
80+
```json
81+
{
82+
"name": "UMBRACO__CMS__Global__MainDomLock",
83+
"value": "FileSystemMainDomLock",
84+
"slotSetting": false
85+
},
86+
{
87+
"name": "UMBRACO__CMS__Hosting__LocalTempStorageLocation",
88+
"value": "EnvironmentTemp",
89+
"slotSetting": false
90+
},
91+
{
92+
"name": "UMBRACO__CMS__Examine__LuceneDirectoryFactory",
93+
"value": "TempFileSystemDirectoryFactory",
94+
"slotSetting": false
95+
}
96+
```
97+
98+
## Steps to set up an environment
6799

68100
1. Create an Azure SQL database
69101
2. Install Umbraco on your backoffice administrative environment and ensure to use your Azure SQL Database

0 commit comments

Comments
 (0)