0

The Issue

I am currently in the process of integrating a pre-rendering service for SEO optimization, however we use an Azure App Service Plan to scale up or down when necessary.

One of the steps for setting up the proper configuration requires placing an applicationHost.xdt file in the /site/ directory, which is one level above the /site/wwwroot directory where the application itself gets deployed to.

What steps should I take in order to have the applicationHost.xdt file persist to new instances spawned by the scaling process?

Steps I have taken to solve the issue

So far I have been Googling a lot, but haven't succeeded in finding a lot of documentation on using an applicationHost.xdt file in combination with an Azure App Service Plan.

I am able to upload the file to an instance manually, however I have assumed that when we then scale up to more instances the manually uploaded file will not be present on the new instance(s).

Etcetera

  • We are using Prerender.io as pre-rendering service.
  • Should there be an easier to set-up & similarly priced service available, we would be open to suggestions as we are in an exploratory phase regarding pre-rendering.
4

1 回答 1

0

假设这不是问题，因为 azure app 下的所有文件都在所有实例之间共享。你可以在这个 Kudu wiki 中查看它：Persisted files。在我的测试中，所有实例都将保留该文件。

关于上传applicationHost.xdt，您不必手动进行，有一个 IIS 管理器站点扩展可以让您非常轻松地创建 XDT 文件。它将为您提供一些示例 XDT。

于 2020-01-21T14:35:41.703 回答