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/deployment-zip-push.md
+16-6Lines changed: 16 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.devlang: multiple
13
13
ms.topic: article
14
14
ms.tgt_pltfrm: multiple
15
15
ms.workload: na
16
-
ms.date: 12/06/2017
16
+
ms.date: 05/29/2018
17
17
ms.author: glenga
18
18
19
19
---
@@ -45,15 +45,25 @@ The .zip file that you use for push deployment must contain all of the project f
45
45
46
46
When you are developing on a local computer, it's easy to create a .zip file of the function app project folder on your development computer.
47
47
48
-
However, you might have created your functions by using the editor in the Azure portal. To download your function app project from the portal:
48
+
However, you might have created your functions by using the editor in the Azure portal. You can download an existing function app project in one of these ways:
49
49
50
-
1. Sign in to the [Azure portal](https://portal.azure.com), and then go to your function app.
50
+
+**From the Azure portal:**
51
51
52
-
2. On the **Overview** tab, select **Download app content**. Select your download options, and then select **Download**.
52
+
1. Sign in to the [Azure portal](https://portal.azure.com), and then go to your function app.
53
53
54
-

54
+
2. On the **Overview** tab, select **Download app content**. Select your download options, and then select **Download**.
55
55
56
-
The downloaded .zip file is in the correct format to be republished to your function app by using .zip push deployment.
56
+

57
+
58
+
The downloaded .zip file is in the correct format to be republished to your function app by using .zip push deployment. The portal download can also add the files needed to open your function app directly in Visual Studio.
59
+
60
+
+**Using REST APIs:**
61
+
62
+
Use the following deployment GET API to download the files from your `<function_app>` project:
Including `/site/wwwroot/` makes sure your zip file includes only the function app project files and not the entire site. If you are not already signed in to Azure, you will be asked to do so. Note that sending a POST request to the `api/zip/` API is discoraged in favor of the zip deployment method described in this topic.
57
67
58
68
You can also download a .zip file from a GitHub repository. Keep in mind that when you download a GitHub repository as a .zip file, GitHub adds an extra folder level for the branch. This extra folder level means that you can't deploy the .zip file directly as you downloaded it from GitHub. If you're using a GitHub repository to maintain your function app, you should use [continuous integration](functions-continuous-deployment.md) to deploy your app.
Copy file name to clipboardExpand all lines: articles/cognitive-services/LUIS/Add-example-utterances.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.author: v-geberr
16
16
17
17
Utterances are examples of user questions or commands. To teach Language Understanding (LUIS), you need to add [example utterances](luis-concept-utterance.md) to an [intent](luis-concept-intent.md).
18
18
19
-
Generally, you add an utterance first, and then you create entities and label utterances on the intent page. If you would rather create entities first, see [Add entities](Add-entities.md).
19
+
Generally, you add an utterance first, and then you create entities and label utterances on the intent page. If you would rather create entities first, see [Add entities](luis-how-to-add-entities.md).
20
20
21
21
## Add an utterance
22
22
On an intent page, enter a relevant utterance you expect from your users, such as `book 2 adult business tickets to Paris tomorrow on Air France` in the text box below the intent name, and then press Enter.
@@ -75,7 +75,7 @@ For example, if you wanted to create a list of types of drink and you selected t
75
75
76
76

77
77
78
-
This list of drinks has only one drink type, water. You can add more drink types by labeling other utterances, or by editing the entity from the **Entities** in the left navigation. [Editing](add-entities.md#add-list-entities) the entities gives you the options of entering additional items with corresponding synonyms or [importing](add-entities.md#import-list-entity-values) a list.
78
+
This list of drinks has only one drink type, water. You can add more drink types by labeling other utterances, or by editing the entity from the **Entities** in the left navigation. [Editing](luis-how-to-add-entities.md#add-list-entities) the entities gives you the options of entering additional items with corresponding synonyms or [importing](luis-how-to-add-entities.md#import-list-entity-values) a list.
79
79
80
80
See [Data Extraction](luis-concept-data-extraction.md#list-entity-data) to learn more about extracting list entities from the endpoint JSON query response. Try the [quickstart](luis-quickstart-intent-and-list-entity.md) to learn more about how to use a list entity.
81
81
@@ -102,7 +102,7 @@ Composite entities are created from **Entities**. You can't create a composite e
102
102
103
103
Assuming the utterance, `book 2 tickets from Seattle to Cairo`, a composite utterance can return entity information of the count of tickets (2), the origin (Seattle), and destination (Cairo) locations in a single parent entity.
104
104
105
-
Follow these [steps](Add-entities.md#add-prebuilt-entity) to add the **number** prebuilt entity. After the entity is created, the `2` in the utterance is blue, indicating it is a labeled entity. Prebuilt entities are labeled by LUIS. You can't add or remove the prebuilt entity label from a single utterance. You can only add or remove all the prebuilt labels by adding or removing the prebuilt entity from the application.
105
+
Follow these [steps](luis-how-to-add-entities.md#add-prebuilt-entity) to add the **number** prebuilt entity. After the entity is created, the `2` in the utterance is blue, indicating it is a labeled entity. Prebuilt entities are labeled by LUIS. You can't add or remove the prebuilt entity label from a single utterance. You can only add or remove all the prebuilt labels by adding or removing the prebuilt entity from the application.
106
106
107
107
Follow these [steps](#add-hierarchical-entity-and-label) to create a **Location** hierarchical entity. Label the origin and destination locations in the example utterance.
108
108
@@ -161,16 +161,16 @@ To remove a machine-learned entity label from an utterance, select the entity in
161
161

162
162
163
163
## Add prebuilt entity label
164
-
If you add the prebuilt entities to your LUIS app, you don't need to label utterances with these entities. To learn more about prebuilt entities and how to add them, see [Add entities](Add-entities.md#add-prebuilt-entity).
164
+
If you add the prebuilt entities to your LUIS app, you don't need to label utterances with these entities. To learn more about prebuilt entities and how to add them, see [Add entities](luis-how-to-add-entities.md#add-prebuilt-entity).
165
165
166
166
## Add regular expression entity label
167
-
If you add the regular expression entities to your LUIS app, you don't need to label utterances with these entities. To learn more about regular expression entities and how to add them, see [Add entities](Add-entities.md#add-regular-expression-entities).
167
+
If you add the regular expression entities to your LUIS app, you don't need to label utterances with these entities. To learn more about regular expression entities and how to add them, see [Add entities](luis-how-to-add-entities.md#add-regular-expression-entities).
168
168
169
169
## Create a pattern from an utterance
170
170
See [Add pattern from existing utterance on intent or entity page](luis-how-to-model-intent-pattern.md#add-pattern-from-existing-utterance-on-intent-or-entity-page).
171
171
172
172
## Add pattern.any entity label
173
-
If you add the pattern.any entities to your LUIS app, you can't label utterances with these entities. They are only valid in patterns. To learn more about pattern.any entities and how to add them, see [Add entities](Add-entities.md#add-patternany-entities).
173
+
If you add the pattern.any entities to your LUIS app, you can't label utterances with these entities. They are only valid in patterns. To learn more about pattern.any entities and how to add them, see [Add entities](luis-how-to-add-entities.md#add-patternany-entities).
174
174
175
175
<!--
176
176
Fix this - moved to add-intents.md - how ?
@@ -190,4 +190,4 @@ After you add, edit, or remove utterances, [train](luis-how-to-train.md) and [pu
190
190
191
191
## Next steps
192
192
193
-
After labeling utterances in your intents, you can now create a [composite entity](Add-entities.md).
193
+
After labeling utterances in your intents, you can now create a [composite entity](luis-how-to-add-entities.md).
0 commit comments