Skip to content

Commit 0a8d007

Browse files
committed
fixed h2s
1 parent c5abeee commit 0a8d007

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/app-service/tutorial-php-mysql-app.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This tutorial shows how to create a secure PHP app in Azure App Service connects
2525
* Knowledge of [PHP with Laravel development](https://laravel.com/).
2626
* **(Optional)** To try GitHub Copilot, a [GitHub Copilot account](https://docs.github.com/copilot/using-github-copilot/using-github-copilot-code-suggestions-in-your-editor). A 30-day free trial is available.
2727

28-
## 1. Run the sample
28+
## 1 - Run the sample
2929

3030
First, you set up a sample data-driven app as a starting point. For your convenience, the [sample repository](https://github.com/Azure-Samples/laravel-tasks), includes a [dev container](https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers) configuration. The dev container has everything you need to develop an application, including the database, cache, and all environment variables needed by the sample application. The dev container can run in a [GitHub codespace](https://docs.github.com/en/codespaces/overview), which means you can run the sample on any computer with a web browser.
3131

@@ -75,7 +75,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
7575

7676
::: zone pivot="azure-portal"
7777

78-
## 2. Create App Service, database, and cache
78+
## 2 - Create App Service, database, and cache
7979

8080
In this step, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service, Azure Database for MySQL, and Azure Cache for Redis. For the creation process, you specify:
8181

@@ -133,7 +133,7 @@ Sign in to the [Azure portal](https://portal.azure.com/) and follow these steps
133133
:::column-end:::
134134
:::row-end:::
135135

136-
## 3. Secure connection secrets
136+
## 3 - Secure connection secrets
137137

138138
The creation wizard generated the connectivity variables for you already as [app settings](configure-common.md#configure-app-settings). However, the security best practice is to keep secrets out of App Service completely. You'll move your secrets to a key vault and change your app setting to [Key Vault references](app-service-key-vault-references.md) with the help of Service Connectors.
139139

@@ -423,7 +423,7 @@ The creation wizard puts the MySQL database server behind a private endpoint, so
423423
> [!TIP]
424424
> In the SSH session, only changes to files in `/home` can persist beyond app restarts. Changes outside of `/home` aren't persisted.
425425
426-
## 5 - Change site root
426+
## 7 - Change site root
427427

428428
[Laravel application lifecycle](https://laravel.com/docs/10.x/lifecycle#lifecycle-overview) begins in the **/public** directory instead. The default PHP container for App Service uses Nginx, which starts in the application's root directory. To change the site root, you need to change the Nginx configuration file in the PHP container (*/etc/nginx/sites-available/default*). For your convenience, the sample repository contains a custom configuration file called *default*. As noted previously, you don't want to replace this file using the SSH shell, because the change is outside of `/home` and will be lost after an app restart.
429429

@@ -449,7 +449,7 @@ The creation wizard puts the MySQL database server behind a private endpoint, so
449449
:::column-end:::
450450
:::row-end:::
451451

452-
## 6 - Browse to the app
452+
## 8 - Browse to the app
453453

454454
:::row:::
455455
:::column span="2":::
@@ -474,7 +474,7 @@ The creation wizard puts the MySQL database server behind a private endpoint, so
474474
> [!TIP]
475475
> The sample application implements the [cache-aside](/azure/architecture/patterns/cache-aside) pattern. When you reload the page after making data changes, **Response time** in the webpage shows a much faster time because it's loading the data from the cache instead of the database.
476476
477-
## 7 - Stream diagnostic logs
477+
## 9 - Stream diagnostic logs
478478

479479
Azure App Service captures all messages logged to the console to assist you in diagnosing issues with your application. The sample app outputs console log messages in each of its endpoints to demonstrate this capability. By default, Laravel's logging functionality (for example, `Log::info()`) outputs to a local file. Your `LOG_CHANNEL` app setting from earlier makes log entries accessible from the App Service log stream.
480480

0 commit comments

Comments
 (0)