网站/Web服务部署环境差异/监控？
我公司的系统是由 ASP.NET 网站、Web 服务、Windows 服务和数据库的集合构建的。 （总共大约 40 个）
我们维护三个环境 - QA、PREPROD 和 LIVE； 但是管理每个环境中安装（和运行）的内容确实很痛苦。 我们似乎花了更多的时间来调试已安装的内容和内容。 在实际开发功能的每个环境中工作。
我正在寻找环境级别的“差异”工具 - 它会告诉我环境之间有什么不同，每个环境上运行哪些服务等等。
是否有类似的现有工具？
谢谢！
My companies' system is build from a collection of ASP.NET websites, webservices, windows services and databases. (around 40 all told)
We maintain three environments - QA, PREPROD and LIVE; but managing what is installed (and working) on each environment is a real pain. We seem to spend more time debugging what is installed & working in each environment that actually developing features.
I'm looking for a "diff" tool at the environment level - something that will tell me what is different between environments, which services are running on each environment etc etc.
Is there any existing tool out there like this?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我的开发团队目前正在使用名为
ConfigMerge的工具（在 CodePlex 上提供）来帮助我们对 web.config 文件进行源代码控制。 您可能不太关心 SCM，但是这样的工具可以帮助您管理配置文件的部署，因为您可以保留所有服务器通用的单个文件，并分解需要为每个服务器修改的特定 XML 元素。服务器。 让 ConfigMerge 工具创建最终结果并进行部署。这并不能帮助您进行“配置差异”，但可能有助于减少这样做的需要。
My development team is currently using a tool called
ConfigMerge(available on CodePlex) to help us source-control our web.config files. You may not care much about SCM, but a tool like that could help you manage deployments of config files because you could keep a single file that is common to all your servers, and break out the particular XML elements that need to be modified for each server. Let the ConfigMerge tool create the final result and deploy that.That doesn't help you do a "configuration diff", but it might help reduce the need to.
我们使用构建服务器，负责在成功构建我们的开发环境时自动部署站点、服务等。
因为我们使用的是 TFSBuild，所以我们使用 TFSDeployer 来监视构建质量设置。 当它切换到“暂存”时，一些 powershell 脚本会执行以将构建移动到我们的暂存环境中。
对于生产，我们还使用 TFSDeployer，但做了一个小改动。 它将其移动到生产服务器上的备份文件夹中，而不是直接转到生产文件夹。 然后基础设施团队手动将其从他们的最终位置复制到。 这可以确保没有人意外地部署到生产中。
总而言之，我们花了几周的时间来设置并解决所有问题。 从那时起，每个人都更加快乐，我们总是确切地知道每个环境中的情况。
We utilize a build server which is responsible for auto deploying sites, services, etc on successful builds to our dev environment.
Because we are using TFSBuild, we use TFSDeployer which monitors the Build Quality setting. When it is flipped to "staging", some powershell scripts execute to move the build into our staging environment.
For production, we also use TFSDeployer with one minor change. Instead of going directly to the production folders, it moves it into backup folders on the production servers. Then the infrastructure team manually copies it from their to the final resting place. This ensures that no one accidentally deploys to production.
All told it took a couple weeks to set up and work out any kinks. Since then everyone is happier and we always know exactly what is in each environment.
添加到所有所说的，您可能还想使用 FinalBuilder，它是一个令人惊叹的构建自动化工具，它为我节省了很多时间做与您所做的类似的事情，它可以自动化整个过程，编译 Visual studio 项目，文件比较，FTP。
希望这可以帮助。
add to what all said, you might also want to use FinalBuilder, it is amazing tool for build automation it has saved me a lot of time doing things similar to what you do, it can automate the whole process, Compiling Visual studio project, file compare, FTPing.
hope this helps.
我能想到的最接近的是 Visual Studio Team 系统部署设计器。
您可以设计系统模型及其逻辑部署架构，并且可以根据物理部署对其进行验证。 例如，您可以验证虚拟目录是否设置正确，检查组件和服务器的版本和补丁等...
您还可以创建报告“显示每个图表以及每个应用程序的所有资源和设置的列表”部署图上的逻辑服务器、端点或区域 您还可以在报告中包含部署图验证错误和警告的列表 应用程序开发和基础架构团队可以使用此报告共享评估应用程序需求和部署图之间的冲突所需的信息。数据中心政策。”
The closest thing I can think of is the Visual Studio Team System Deployment Designer.
You can design a model of the system and it's logical deployment architecture, and you can validate that against the physical deployment. For instance, you can validate that virtual directories are set up correctly, check against versions and patches of components and servers, etc....
You can also create reports "showing each diagram and a list of all the resources and settings for each application, logical server, endpoint, or zone on the deployment diagram. You can also include a list of deployment diagram validation errors and warnings in the report. Application development and infrastructure teams can use this report to share information needed to evaluate conflicts between application requirements and datacenter policy."