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/CustomizingAzdParameters.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,6 @@ By default this template will use the environment name as the prefix to prevent
16
16
| `AZURE_ENV_MODEL_NAME` | string | `gpt-4o` | Specifies the GPT model name (allowed values: `gpt-4o`).
17
17
|`AZURE_ENV_MODEL_VERSION`| string |`2024-08-06`| Specifies the GPT model version (allowed values: `2024-08-06`). |
18
18
|`AZURE_ENV_MODEL_CAPACITY`| integer |`30`| Sets the model capacity (choose based on your subscription's available GPT capacity). |
19
-
|`USE_LOCAL_BUILD`| boolean |`false`| Indicates whether to use a local container build for deployment. |
20
19
|`AZURE_ENV_IMAGETAG`| boolean |`latest`| Set the Image tag Like (allowed values: latest, dev, hotfix) |
21
20
|`AZURE_ENV_LOG_ANALYTICS_WORKSPACE_ID`| string |`<Existing Workspace Id>`| Reuses an existing Log Analytics Workspace instead of provisioning a new one. |
Copy file name to clipboardExpand all lines: docs/DeploymentGuide.md
+18-21Lines changed: 18 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -173,40 +173,37 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain
173
173
- This deployment will take *4-6 minutes* to provision the resources in your account and set up the solution with sample data.
174
174
- If you encounter an error or timeout during deployment, changing the location may help, as there could be availability constraints for the resources.
175
175
176
-
5. Once the deployment has completed successfully, open the [Azure Portal](https://portal.azure.com/), go to the deployed resource group, find the App Service, and get the app URL from `Default domain`.
176
+
5. Once the deployment has completed successfully:
177
+
> Please check the terminal or console output for details of the successful deployment. It will display the Name, Endpoint (Application URL), and Azure Portal URL for both the Web and API Azure Container Apps.
177
178
178
-
6. If you are done trying out the application, you can delete the resources by running `azd down`.
179
+

179
180
180
-
### Publishing Local Build Container to Azure Container Registry
181
+
- You can find the Azure portal link in the screenshot above. Click on it to navigate to the corresponding resource group in the Azure portal.
181
182
182
-
If you need to rebuild the source code and push the updated container to the deployed Azure Container Registry, follow these steps:
183
+
> #### Important Note : Before accessing the application, ensure that all **[Post Deployment Steps](#post-deployment-steps)** are fully completed, as they are critical for the proper configuration of **Data Ingestion** and **Authentication** functionalities.
183
184
184
-
1. Set the environment variable `USE_LOCAL_BUILD` to `True`:
185
+
7. If you are done trying out the application, you can delete the resources by running `azd down`.
186
+
187
+
## Post Deployment Steps
188
+
1. Optional: Publishing Local Build Container to Azure Container Registry
189
+
190
+
If you need to rebuild the source code and push the updated container to the deployed Azure Container Registry, follow these steps:
185
191
186
192
- **Linux/macOS**:
187
193
```bash
188
-
export USE_LOCAL_BUILD=True
194
+
cd ./infra/scripts/
195
+
./docker-build.sh
189
196
```
190
197
191
198
- **Windows (PowerShell)**:
192
199
```powershell
193
-
$env:USE_LOCAL_BUILD = $true
200
+
cd .\infra\scripts\
201
+
.\docker-build.ps1
194
202
```
195
-
2. Run the `az login` command
196
-
```bash
197
-
az login
198
-
```
199
203
200
-
3. Run the `azd up` command again to rebuild and push the updated container:
201
-
```bash
202
-
azd up
203
-
```
204
-
205
-
This will rebuild the source code, package it into a container, and push it to the Azure Container Registry associated with your deployment.
206
-
207
-
## Post Deployment Steps
204
+
This will create a new Azure Container Registry, rebuild the source code, package it into a container, and push it to the Container Registry created.
208
205
209
-
1. **Register Schema Files**
206
+
2. **Register Schema Files**
210
207
211
208
> Want to customize the schemas for your own documents? [Learn more about adding your own schemas here.](./CustomizeSchemaData.md)
212
209
@@ -236,7 +233,7 @@ This will rebuild the source code, package it into a container, and push it to t
0 commit comments