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: docs/aca/README-ACA.md
+21-15Lines changed: 21 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,15 +78,15 @@ All prerequisites are already installed in the container. You can skip to the [
78
78
***Important**: Ensure you can run `pwsh.exe` from a PowerShell command. If this fails, you likely need to upgrade PowerShell.
79
79
80
80
81
-
>NOTE: Your Azure Account must have `Microsoft.Authorization/roleAssignments/write` permissions, such as [User Access Administrator](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles#user-access-administrator) or [Owner](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles#owner).
81
+
>[!WARNING] Your Azure Account must have `Microsoft.Authorization/roleAssignments/write` permissions, such as [User Access Administrator](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles#user-access-administrator) or [Owner](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles#owner).
82
82
83
83
### Starting from scratch
84
84
85
85
You can clone this repo and change directory to the root of the repo. Or you can run `azd init -t Azure-Samples/azure-search-openai-demo-java`.
86
86
87
87
Once you have the project available locally, run the following commands if you don't have any pre-existing Azure services and want to start from a fresh deployment.
88
88
> [!IMPORTANT]
89
-
> All the commands below assume be run from the `deploy/aca` folder
89
+
> All the commands below must be run from the `deploy/aca` folder
90
90
91
91
1. Run
92
92
@@ -103,13 +103,13 @@ Once you have the project available locally, run the following commands if you d
103
103
* This will provision Azure resources and deploy this sample to those resources, including building the search index based on the files found in the `./data` folder.
104
104
* For the target location, the regions that currently support the models used in this sample are **East US**, **France Central**, **South Central US**, **UK South**, and **West Europe**. For an up-to-date list of regions and models, check [here](https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models)
105
105
106
-
3. After the application has been successfully deployed you will see a frontend app URL printed to the console. Click that URL to interact with the application in your browser.
106
+
3. After the application has been successfully deployed you will see a web app URL printed to the console. Click that URL to interact with the application in your browser.
107
107
108
108
It will look like the following:
109
109
110
-

110
+

111
111
112
-
> NOTE: It may take a minutefor the application to be fully deployed.
112
+
> NOTE: It may take few minutesforthe indexer app to consume the pdf ingestion request messages. You can monitor the ingestion process by checking the log stream of the indexer appin the Azure Portal.
113
113
114
114
### Deploying with existing Azure resources
115
115
@@ -158,6 +158,19 @@ If you've changed the infrastructure files (`infra` folder or `azure.yaml`), the
158
158
159
159
```shell
160
160
azd up
161
+
```
162
+
> WARNING: when you run `azd up` multiple times to redeploy infrastructure, make sure to set the following parameters in `infra/main.parameters.json` to `true` to avoid container apps images from being overridden with default "mcr.microsoft.com/azuredocs/containerapps-helloworld" image:
163
+
164
+
```json
165
+
"apiAppExists": {
166
+
"value": true
167
+
},
168
+
"webAppExists": {
169
+
"value": true
170
+
},
171
+
"indexerAppExists": {
172
+
"value": true
173
+
}
161
174
```
162
175
163
176
### Examples of an azd deployment changing the default chatgpt deployment model
@@ -203,7 +216,7 @@ azd up
203
216
cd app
204
217
```
205
218
206
-
3. Run the `./start.ps1` (Windows) or `./start.sh` (Linux/Mac) scripts or run the "VS Code Task: Start App" to start the project locally.
219
+
3. Run the `./start-compose.ps1` (Windows) or `./start-compose.sh` (Linux/Mac) scripts or run the "VS Code Task: Start App" to start the project locally.
207
220
4. Wait for the docker compose to start all the containers (web, api, indexer) and refresh your browser to [http://localhost](http://localhost)
208
221
209
222
### UI Navigation
@@ -242,7 +255,7 @@ To see the performance data, go to the Application Insights resource in your res
242
255
To inspect the performance of chat requests, use the "Drill into Samples" button to see end-to-end traces of all the API calls made for any chat request.
243
256
Under "Trace & Events" panel you can review custom Java informational logs to better understand content of OpenAI requests and responses.
To see any exceptions and server errors, navigate to the "Investigate -> Failures" blade and use the filtering tools to locate a specific exception. You can see Java stack traces on the right-hand side.
248
261
@@ -396,12 +409,5 @@ Here are the most common failure scenarios and solutions:
396
409
6. After running `./app/start.ps1` on Windows PowerShell you get `The file C:\path\to\azure-search-openai-demo-java\app\start.ps1 is not digitally signed. You cannot run this script on the current system`. Try to run `Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass` and try to re-run `./app/start.ps1`
397
410
398
411
7. After running `./app/start.ps1` or `./app/start.sh` you get `"Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project myproject: Fatal error compiling: invalid target release: 17"`. It means you are not using JDK 17 but a previous version. Be sure to set the `JAVA_HOME` env variable to your Java 17 installation directory and update your `PATH` env variable to have the Java 17 bin folder as the first occurrence amongst the listed directories. More info [here](https://learn.microsoft.com/en-us/java/openjdk/install)
399
-
8. After running `./app/start.sh` on Ubuntu 16.04 or later, the first time you try to create a virtual environment with Python 3.6, Python 3.7, Python 3.8 or Python 3.9, you'll get the following error `"The virtual environment was not created successfully because ensurepip is not available"`. Just follow the hint provided in the error message and run `apt-get install python3-venv` to install the missing packages. More info [here](https://www.softwarepragmatism.com/cannot-create-a-python-virtual-environment-on-ubuntu-ensurepip-is-not-available)
400
-
9. While running `azd up`in VS Code Dev Containers you got this error `".. Maven: failed finding mvnw in repository path: exec: /azure-search-openai-demo-java/app/backend/mvnw: permission denied "`. Run `chmod +x ./azure-search-openai-demo-javaapp/backend/mvnw` to fix it and rerun `azd up`.
401
-
10. Github App CI pipeline might fail in some scenarios where the provisioned App Service instance doesn't have "Basic Auth Publishing Credentials" enabled in your subscription. To fix it, you can go to your App Service instance in Azure Portal, click on "Settings/Configuration(Panel)->General Settins (Tab)" and flag to ON the "Basic Auth Publishing Credentials" checkbox group. Or you can run the following azd cli commands:
For more details see this [issue](https://github.com/Azure-Samples/azure-search-openai-demo-java/issues/7).
413
+
8. While running `azd up` in VS Code Dev Containers you got this error `".. Maven: failed finding mvnw in repository path: exec: /azure-search-openai-demo-java/app/backend/mvnw: permission denied "`. Run `chmod +x ./azure-search-openai-demo-javaapp/backend/mvnw` to fix it and rerun `azd up`.
Copy file name to clipboardExpand all lines: docs/aks/README-AKS.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ You can clone this repo and change directory to the root of the repo. Or you can
88
88
Once you have the project available locally, run the following commands if you don't have any pre-existing Azure services and want to start from a fresh deployment.
89
89
90
90
> [!IMPORTANT]
91
-
> All the commands below assume be run from the `deploy/aks` folder
91
+
> All the commands below must be run from the `deploy/aks` folder
92
92
93
93
1. Run
94
94
@@ -192,6 +192,22 @@ azd env set AZURE_SEARCH_SERVICE_LOCATION "eastus2" # Region of the ACS service
192
192
193
193
azd up
194
194
```
195
+
### Running locally
196
+
197
+
1. Run
198
+
199
+
```shell
200
+
az login
201
+
```
202
+
203
+
2. Change dir to `app`
204
+
205
+
```shell
206
+
cd app
207
+
```
208
+
209
+
3. Run the `./start-compose.ps1` (Windows) or `./start-compose.sh` (Linux/Mac) scripts or run the "VS Code Task: Start App" to start the project locally.
210
+
4. Wait for the docker compose to start all the containers (web, api, indexer) and refresh your browser to [http://localhost](http://localhost)
0 commit comments