Skip to content

Commit 91491b8

Browse files
Merge pull request #281981 from msangapu-msft/patch-1
Update deploy-run-package.md
2 parents 94cc833 + f9c0344 commit 91491b8

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/app-service/deploy-run-package.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.author: cephalin
1010

1111
# Run your app in Azure App Service directly from a ZIP package
1212

13+
> [!NOTE]
14+
> Run from package is not supported for Python apps. When deploying a ZIP file of your Python code, you need to set a flag to enable Azure build automation. The build automation will create the Python virtual environment for your app and install any necessary requirements and package needed. See [build automation](quickstart-python.md?tabs=flask%2Cmac-linux%2Cazure-cli%2Czip-deploy%2Cdeploy-instructions-azportal%2Cterminal-bash%2Cdeploy-instructions-zip-azcli#enable-build-automation) for more details.
15+
1316
In [Azure App Service](overview.md), you can run your apps directly from a deployment ZIP package file. This article shows how to enable this functionality in your app.
1417

1518
All other deployment methods in App Service have something in common: your files are deployed to *D:\home\site\wwwroot* in your app (or */home/site/wwwroot* for Linux apps). Since the same directory is used by your app at runtime, it's possible for deployment to fail because of file lock conflicts, and for the app to behave unpredictably because some of the files are not yet updated.

0 commit comments

Comments
 (0)