IIS暂存和生产交换 [英] IIS Staging and Production swap

问题描述

我正在研究一种在IIS服务器上集成暂存环境的方法，在此环境中可以在与生产环境交换应用程序之前对其进行预热.

I'm researching a way to integrate a staging environment on our IIS Server, where it is possible to warm up the application before swapping it with the production environment.

我能找到的唯一真正的解决方案是:

The only real solution I can find is:

1. 交换目录设置

1. Swapping directory settings

• 对我来说这听起来很缓慢，因为IIS必须在交换后编译并预热新目录.(我是否假设正确?)

在分阶段预热后，有两个站点，并交换绑定.

Have two sites, and swap the bindings, after staging has been warmed up.

前两种情况似乎很容易破解，而且容易出错.

The two first scenarios seem hacky, and error prone.

显然我必须缺少一些东西.因此，专家们，我求助于您！

Obviously there must be something I am missing. So I turn to you, the experts!

Ps.我们使用的是Windows Server 2012，IIS v8.0

Ps. We are on Windows Server 2012, IIS v8.0

推荐答案

选项1和2将导致iis应用程序池回收.取决于您经营的业务类型，如何处理会话等，这可能不重要，

Options 1 and 2 are going to cause the iis app pool to recycle. This might or might not be a big deal depending on the type of business you run, how you handle sessions etc.

选项3似乎是更合适的选项，如果您想横向扩展并添加其他计算机，则可以为您提供一些灵活性.这是向已经熟悉该模式的未来开发人员解释的最简单的方法.

Option 3 seems like the more graceful option and gives you some flexibility if you ever want to scale out and add additional machines. And it's the easiest to explain to future developers already familiar with the pattern.

http://martinfowler.com/bliki/BlueGreenDeployment.html

但是，它确实要求您通过Powershell或使用的任何集成工具(可能很棘手)访问负载平衡.

It does however require you to access your load balance via Powershell or whatever integration tool you are using which might be tricky.

这篇关于IIS暂存和生产交换的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！