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/app-service/tutorial-nodejs-mongodb-app.md
+13-21Lines changed: 13 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,19 +62,18 @@ Sign in to the [Azure portal](https://portal.azure.com/) and follow these steps
62
62
1. *Region*→ Any Azure region near you.
63
63
1. *Name*→**msdocs-expressjs-mongodb-XYZ** where *XYZ* is any three random characters. This name must be unique across Azure.
64
64
1. *Runtime stack*→**Node 16 LTS**.
65
-
**Cosmos DB API for MongoDB** is selected for you by default as the database engine. Azure Cosmos DB is a cloud native database offering a 100% MongoDB compatible API.
66
65
1. *Hosting plan*→**Basic**. When you're ready, you can [scale up](manage-scale-up.md) to a production pricing tier later.
67
-
1. Note the database name that's generated for you (*\<app-name>-database*). You'll need it later.
66
+
1. **Cosmos DB API for MongoDB** is selected by default as the database engine. Azure Cosmos DB is a cloud native database offering a 100% MongoDB compatible API. Note the database name that's generated for you (*\<app-name>-database*). You'll need it later.
68
67
1. Select **Review + create**.
69
-
After validation completes, select **Create**.
68
+
1. After validation completes, select **Create**.
70
69
:::column-end:::
71
70
:::column:::
72
71
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-create-app-cosmos-2.png" alt-text="A screenshot showing how to configure a new app and database in the Web App + Database wizard." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-create-app-cosmos-2.png":::
73
72
:::column-end:::
74
73
:::row-end:::
75
74
:::row:::
76
75
:::column span="2":::
77
-
**Step 3.** The deployment takes a few minutes to complete, and creates the following resources:
76
+
**Step 3.** The deployment takes a few minutes to complete. Once deployment completes, select the **Go to resource** button. You're taken directly to the App Service app, but the following resources are created:
78
77
- **Resource group**→ The container for all the created resources.
79
78
- **App Service plan**→ Defines the compute resources for App Service. A Linux plan in the *Basic* tier is created.
80
79
- **App Service**→ Represents your app and runs in the App Service plan.
@@ -83,7 +82,7 @@ Sign in to the [Azure portal](https://portal.azure.com/) and follow these steps
83
82
- **Network interface**→ Represents a private IP address for the private endpoint.
84
83
- **Cosmos DB API for MongoDB**→ Accessible only from behind the private endpoint. A database and a user are created for you on the server.
85
84
- **Private DNS zone**→ Enables DNS resolution of the Cosmos DB server in the virtual network.
86
-
Once deployment completes, select the **Go to resource** button. You're taken directly to the App Service app.
85
+
87
86
:::column-end:::
88
87
:::column:::
89
88
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-create-app-cosmos-3.png" alt-text="A screenshot showing the deployment process completed." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-create-app-cosmos-3.png":::
@@ -128,9 +127,7 @@ The creation wizard generated the MongoDB URI for you already, but your app need
128
127
:::row:::
129
128
:::column span="2":::
130
129
**Step 4.**
131
-
1. Using the same steps in **Step 2**, create another application setting with the following parameters:
132
-
- **Name**: *DATABASE_URL*
133
-
- **Value**: Paste the value you copied from the `MONGODB_URI` connection string.
130
+
1. Using the same steps in **Step 2**, create an app setting named *DATABASE_URL* and set the value to the one you copied from the `MONGODB_URI` connection string (i.e. `mongodb://...`).
134
131
1. In the menu bar at the top, select **Save**.
135
132
1. When prompted, select **Continue**.
136
133
:::column-end:::
@@ -188,8 +185,7 @@ In this step, you'll configure GitHub deployment using GitHub Actions. It's just
188
185
1. In **Organization**, select your account.
189
186
1. In **Repository**, select **msdocs-nodejs-mongodb-azure-sample-app**.
190
187
1. In **Branch**, select **main**.
191
-
1. In the top menu, select **Save**.
192
-
App Service commits a workflow file into the selected GitHub repository, in the `.github/workflows` directory.
188
+
1. In the top menu, select **Save**. App Service commits a workflow file into the chosen GitHub repository, in the `.github/workflows` directory.
193
189
:::column-end:::
194
190
:::column:::
195
191
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-deploy-sample-code-5.png" alt-text="A screenshot showing how to configure CI/CD using GitHub Actions." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-deploy-sample-code-5.png":::
@@ -199,30 +195,28 @@ In this step, you'll configure GitHub deployment using GitHub Actions. It's just
199
195
:::column span="2":::
200
196
**Step 6.** In the Deployment Center page:
201
197
1. Select **Logs**. A deployment run is already started.
202
-
1. In the log item for the deployment run, select **Build/Deploy Logs**.
203
-
You're taken to your GitHub repository and see that the GitHub action is running. The workflow file defines two separate stages, build and deploy.
198
+
1. In the log item for the deployment run, select **Build/Deploy Logs**.
204
199
:::column-end:::
205
200
:::column:::
206
201
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-deploy-sample-code-6.png" alt-text="A screenshot showing how to open deployment logs in the deployment center." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-deploy-sample-code-6.png":::
207
202
:::column-end:::
208
203
:::row-end:::
209
204
:::row:::
210
205
:::column span="2":::
211
-
**Step 7.** Wait for the GitHub run to show a status of **Complete**. It takes about 15 minutes.
206
+
**Step 7.**You're taken to your GitHub repository and see that the GitHub action is running. The workflow file defines two separate stages, build and deploy. Wait for the GitHub run to show a status of **Complete**. It takes about 15 minutes.
212
207
:::column-end:::
213
208
:::column:::
214
209
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-deploy-sample-code-7.png" alt-text="A screenshot showing a GitHub run in progress." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-deploy-sample-code-7.png":::
215
210
:::column-end:::
216
211
:::row-end:::
217
212
218
-
## 4 - Browse to the app
213
+
## 4. Browse to the app
219
214
220
215
:::row:::
221
216
:::column span="2":::
222
217
**Step 1.** In the App Service page:
223
218
1. From the left menu, select **Overview**.
224
-
1. Select the URL of your app.
225
-
You can also navigate directly to `https://<app-name>.azurewebsites.net`.
219
+
1. Select the URL of your app. You can also navigate directly to `https://<app-name>.azurewebsites.net`.
226
220
:::column-end:::
227
221
:::column:::
228
222
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-browse-app-1.png" alt-text="A screenshot showing how to launch an App Service from the Azure portal." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-browse-app-1.png":::
@@ -256,8 +250,7 @@ Azure App Service captures all messages logged to the console to assist you in d
256
250
:::row-end:::
257
251
:::row:::
258
252
:::column span="2":::
259
-
**Step 2.** From the left menu, select **Log stream**.
260
-
You see the logs for your app, including platform logs and logs from inside the container.
253
+
**Step 4.** From the left menu, select **Log stream**. You see the logs for your app, including platform logs and logs from inside the container.
261
254
:::column-end:::
262
255
:::column:::
263
256
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-stream-diagnostic-logs-2.png" alt-text="A screenshot showing how to view the log stream in the Azure portal." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-stream-diagnostic-logs-2.png":::
@@ -272,7 +265,7 @@ Azure App Service provides a web-based diagnostics console named [Kudu](./resour
272
265
:::column span="2":::
273
266
**Step 1.** In the App Service page:
274
267
1. From the left menu, select **Advanced Tools**.
275
-
1. Select **Go**.
268
+
1. Select **Go**. You can also navigate directly to `https://<app-name>.scm.azurewebsites.net`.
276
269
:::column-end:::
277
270
:::column:::
278
271
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-1.png" alt-text="A screenshot showing how to navigate to the App Service Kudu page." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-1.png":::
@@ -304,8 +297,7 @@ Azure App Service provides a web-based diagnostics console named [Kudu](./resour
304
297
:::row-end:::
305
298
:::row:::
306
299
:::column span="2":::
307
-
**Step 5.** From the left menu, select **Log stream**.
308
-
You see the logs for your app, including platform logs and logs from inside the container.
300
+
You can see the deployed folder structure and click to browse and view the files.
309
301
:::column-end:::
310
302
:::column:::
311
303
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-5.png" alt-text="A screenshot of deployed files in the wwwroot directory." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-5.png":::
0 commit comments