Browse Source

Update deployment-iis.md

pull/21231/head
Engincan VESKE 1 year ago
committed by GitHub
parent
commit
3c3e2ed904
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 2
      docs/en/solution-templates/layered-web-application/deployment/deployment-iis.md

2
docs/en/solution-templates/layered-web-application/deployment/deployment-iis.md

@ -262,7 +262,7 @@ To enable and view stdout logs:
1. Navigate to the site's deployment folder on the hosting system.
2. If the logs folder isn't present, create the folder. For instructions on how to enable MSBuild to create the logs folder in the deployment automatically, see the [Directory structure topic](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/directory-structure?view=aspnetcore-8.0).
3. Edit the `web.config` file. Set `stdoutLogEnabled` to `true` and change the `stdoutLogFile` path to point to the logs folder (for example, `.\logs\stdout`). stdout in the path is the log file name prefix. A timestamp, process id, and file extension are added automatically when the log is created. Using stdout as the file name prefix, a typical log file is named s`tdout_20180205184032_5412.log`.
3. Edit the `web.config` file. Set `stdoutLogEnabled` to `true` and change the `stdoutLogFile` path to point to the logs folder (for example, `.\logs\stdout`). stdout in the path is the log file name prefix. A timestamp, process id, and file extension are added automatically when the log is created. Using stdout as the file name prefix, a typical log file is named `stdout_20180205184032_5412.log`.
4. Ensure your application pool's identity has write permissions to the logs folder.
5. Save the updated `web.config` file.
6. Make a request to the app.

Loading…
Cancel
Save