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/functions-deployment-technologies.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -172,7 +172,7 @@ You can use local Git to push code from your local machine to Azure Functions by
172
172
173
173
>__How to use it:__ Follow the instructions in [Local Git deployment to Azure App Service](../app-service/deploy-local-git.md).
174
174
175
-
>__When to use it:__In general, we recommend that you use a different deployment method. When you publish from local Git, you must[manually sync triggers](#trigger-syncing).
175
+
>__When to use it:__To minimize the probability of errors, we generally do not recommend deployment methods that require the additional step of[manually syncing triggers](#trigger-syncing). Instead, we recommend [zip deployment](run-functions-from-deployment-package.md).
176
176
177
177
>__Where app content is stored:__ App content is stored on the file system, which may be backed by Azure Files from the storage account specified when the function app was created.
178
178
@@ -182,17 +182,17 @@ Use cloud sync to sync your content from Dropbox and OneDrive to Azure Functions
182
182
183
183
>__How to use it:__ Follow the instructions in [Sync content from a cloud folder](../app-service/deploy-content-sync.md).
184
184
185
-
>__When to use it:__In general, we recommend other deployment methods. When you publish by using cloud sync, you must [manually sync triggers](#trigger-syncing).
185
+
>__When to use it:__To minimize the probability of errors, we generally do not recommend deployment methods that require the additional step of [manually syncing triggers](#trigger-syncing). Instead, we recommend [zip deployment](run-functions-from-deployment-package.md).
186
186
187
187
>__Where app content is stored:__ The app content is in the cloud store, but a local copy is stored on the app file system, which may be backed by Azure Files from the storage account specified when the function app was created.
188
188
189
189
### FTP
190
190
191
191
You can use FTP to directly transfer files to Azure Functions.
192
192
193
-
>__How to use it:__ Follow the instructions in [Deploy content by using FTP/s](../app-service/deploy-ftp.md).
193
+
>__How to use it:__ Follow the instructions in [Deploy content by using FTP/s](../app-service/deploy-ftp.md). Note that FTP/s deployment is not available in the function app portal, but it can be performed with CLI or PowerShell.
194
194
195
-
>__When to use it:__In general, we recommend other deployment methods. When you publish by using FTP, you must [manually sync triggers](#trigger-syncing).
195
+
>__When to use it:__To minimize the probability of errors, we generally do not recommend deployment methods that require the additional step of [manually syncing triggers](#trigger-syncing). Instead, we recommend [zip deployment](run-functions-from-deployment-package.md).
196
196
197
197
>__Where app content is stored:__ App content is stored on the file system, which may be backed by Azure Files from the storage account specified when the function app was created.
0 commit comments