You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/run-functions-from-deployment-package.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
title: Run your functions from a package file in Azure
3
-
description: Learn how to configure Azure Functions to run your function app from a deployment package file that contains your function app project files.
3
+
description: Learn how to configure Azure Functions to run your function app from a deployment package file that contains your function app project.
4
4
mw-service: azure-functions
5
5
ms.topic: conceptual
6
-
ms.date: 06/21/2024
6
+
ms.date: 06/28/2024
7
7
8
8
# Customer intent: As a function developer, I want to understand how to run my function app from a deployment package file, so I can make my function app run faster and easier to update.
9
9
---
@@ -22,7 +22,7 @@ There are several benefits to running functions from a package file:
22
22
+ Can be deployed to a production app (with restart).
23
23
+ Verifies the files that are running in your app.
24
24
+ Improves the performance of [Azure Resource Manager deployments](functions-infrastructure-as-code.md).
25
-
+Can reduce cold-start times, particularly for JavaScript functions with large npm package trees.
25
+
+Reduces cold-start times, particularly for JavaScript functions with large npm package trees.
26
26
27
27
For more information, see [this announcement](https://github.com/Azure/app-service-announcements/issues/84).
28
28
@@ -66,6 +66,8 @@ This section provides information about how to run your function app from a loca
66
66
67
67
### Considerations for deploying from an on-site package
68
68
69
+
<aname="troubleshooting"></a>
70
+
69
71
+ Using an on-site package is the recommended option for running from the deployment package, except when running on Linux hosted in a Consumption plan.
70
72
+[Zip deployment](#integration-with-zip-deployment) is the recommended way to upload a deployment package to your site.
71
73
+ When not using zip deployment, make sure the `c:\home\data\SitePackages` (Windows) or `/home/data/SitePackages` (Linux) folder has a file named `packagename.txt`. This file contains only the name, without any whitespace, of the package file in this folder that's currently running.
@@ -91,10 +93,10 @@ This section provides information about how to run your function app from a pack
91
93
+ Don't deploy your package to Azure Blob Storage as a public blob. Instead, use a private container with a [shared access signature (SAS)](../storage/common/storage-sas-overview.md) or [use a managed identity](#fetch-a-package-from-azure-blob-storage-using-a-managed-identity) to enable the Functions runtime to access the package.
92
94
+ You must maintain any SAS URLs used for deployment. When an SAS expires, the package can no longer be deployed. In this case, you must generate a new SAS and update the setting in your function app. You can eliminate this management burden by [using a managed identity](#fetch-a-package-from-azure-blob-storage-using-a-managed-identity).
93
95
+ When running on a Premium plan, make sure to [eliminate cold starts](functions-premium-plan.md#eliminate-cold-starts).
94
-
+ When your running on a Dedicated plan, ensure you enable [Always On](dedicated-plan.md#always-on).
96
+
+ When you're running on a Dedicated plan, ensure you enable [Always On](dedicated-plan.md#always-on).
95
97
+ You can use [Azure Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md) to upload package files to blob containers in your storage account.
96
98
97
-
### Manually uploading a package to Blob Storage
99
+
### Manually upload a package to Blob Storage
98
100
99
101
To deploy a zipped package when using the URL option, you must create a .zip compressed deployment package and upload it to the destination. The following procedure deploys to a container in Blob Storage:
100
102
@@ -118,16 +120,12 @@ To deploy a zipped package when using the URL option, you must create a .zip com
118
120
119
121
1. In the **App settings** tab, select **+ Add**.
120
122
121
-
1. Enter the value `WEBSITE_RUN_FROM_PACKAGE` for the **Name**, and paste the URL of your package in Blob Storage as the **Value**.
123
+
1. Enter the value `WEBSITE_RUN_FROM_PACKAGE` for the **Name**, and paste the URL of your package in Blob Storage for the **Value**.
122
124
123
-
1. Select **Apply**. Select **Apply**again, and then select **Confirm** to save the setting and restart the app.
125
+
1. Select **Apply**, and then select **Apply** and **Confirm** to save the setting and restart the function app.
124
126
125
127
Now you can run your function in Azure to verify that deployment of the deployment package .zip file was successful.
126
128
127
-
The following screenshot shows a function app configured to run from a .zip file hosted in Azure Blob storage:
128
-
129
-

130
-
131
129
### Fetch a package from Azure Blob Storage using a managed identity
132
130
133
131
[!INCLUDE [Run from package via Identity](../../includes/app-service-run-from-package-via-identity.md)]
0 commit comments