Skip to content

Commit 851a163

Browse files
Merge branch 'kings-dkm-dev' of https://github.com/microsoft/Document-Knowledge-Mining-Solution-Accelerator into kings-dkm-dev
2 parents cd9ce22 + e13f9ac commit 851a163

1 file changed

Lines changed: 52 additions & 3 deletions

File tree

docs/DeploymentGuide.md

Lines changed: 52 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,52 @@
4444

4545
## Deployment
4646

47-
The automated deployment process is very straightforward and simplified via a single [deployment script](../Deployment/resourcedeployment.ps1) that completes in approximately 10-15 minutes:
47+
### Deploying with AZD
48+
49+
Once you've opened the project in [Codespaces](#github-codespaces), [Dev Containers](#vs-code-dev-containers), or [locally](#local-environment), you can deploy it to Azure by following these steps:
50+
51+
1. Clone the repository or download the project code via command-line:
52+
53+
```cmd
54+
git clone https://github.com/microsoft/Document-Knowledge-Mining-Solution-Accelerator
55+
```
56+
57+
Open the cloned repository in Visual Studio Code and connect to the development container.
58+
59+
```cmd
60+
code .
61+
```
62+
63+
2. Login to Azure:
64+
65+
```shell
66+
azd auth login
67+
```
68+
69+
#### To authenticate with Azure Developer CLI (`azd`), use the following command with your **Tenant ID**:
70+
71+
```sh
72+
azd auth login --tenant-id <tenant-id>
73+
```
74+
75+
3. Provision and deploy all the resources:
76+
77+
```shell
78+
azd up
79+
```
80+
81+
4. Provide an `azd` environment name (e.g., "ckmapp").
82+
5. Select a subscription from your Azure account and choose a location that has quota for all the resources.
83+
-- This deployment will take *7-10 minutes* to provision the resources in your account and set up the solution with sample data.
84+
- If you encounter an error or timeout during deployment, changing the location may help, as there could be availability constraints for the resources.
85+
86+
6. 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`.
87+
88+
7. If you are done trying out the application, you can delete the resources by running `azd down`.
89+
90+
### Post Deployment Script:
91+
92+
The post deployment process is very straightforward and simplified via a single [deployment script](../Deployment/resourcedeployment.ps1) that completes in approximately 20-30 minutes:
4893
4994
### Automated Deployment Steps:
5095
1. Deploy Azure resources.
@@ -56,8 +101,6 @@ The automated deployment process is very straightforward and simplified via a si
56101
6. Update Kubernetes configuration files.
57102
7. Deploy certificates, ingress controller and then application images from Azure Container Registry.
58103
59-
60-
### Execute Deployment Script:
61104
Open PowerShell, change directory where you code cloned, then run the deploy script:
62105
63106
```
@@ -137,3 +180,9 @@ Execute uploadfiles.ps1 file with **-EndpointUrl** parameter as URL in console m
137180
```
138181
.\uploadfiles.ps1 -EndpointUrl https://kmgs<your dns name>.<datacenter>.cloudapp.azure.com
139182
```
183+
184+
If you run into issue with PowerShell script file not being digitally signed, you can execute below command:
185+
186+
```
187+
powershell.exe -ExecutionPolicy Bypass -File ".\uploadfiles.ps1" -EndpointUrl https://kmgs<your dns name>.<datacenter>.cloudapp.azure.com
188+
```

0 commit comments

Comments
 (0)