许多Azure应用服务的部署方法
我们目前使用非常传统的部署方法。开发人员构建了EXE软件包，然后将其交付给将其安装到VM上的运营团队（每个客户一个VM）。我们公司是B2B，客户之间的资源很少共享。
现在，我们正在考虑使用Azure App Services部署软件。
我可以将应用程序部署到Azure App Services，但是向许多客户部署的推荐方法是什么？在线文档在线谈论了很多关于连续部署的讨论，那么我们是否期望我们为每个客户维护部署配置文件吗？
We currently use a very traditional deployment methodology. Developers build EXE packages which are then handed to the operations team who install it onto VMs (one VM per customer). Our company is B2B and resources between customers is rarely shared.
Now, we are looking at using Azure App Services to deploy software.
I can deploy our app to Azure App Services, but what is the recommended way to deploy to many customers? The documentation online talks a lot about continuous deployment, so is the expectation that we maintain deployment profiles for each customer?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我将从探索APServices脚本创建的AZ-CLI开始。然后使用AZ-CLI将您的应用程序部署到不同的客户应用程序服务。关于不同的客户：我将在单个应用程序服务计划中以每个客户的appservice开始，这样您就可以暂时限制成本。
我们使用Azure DevOps构建和发布管道来创建（和更新）应用程序服务以及构建和部署到这些应用程序服务。根据某些条件，我们首先将其部署到开发后，在批准大门进行测试，质量保证和最终生产之后。如今，我们将YAML管道用于大多数任务，但我们从Azure Portal和Az-CLI开始。从手动部署到完全自动化需要花费时间。
I would start with exploring the AZ-CLI to script creation of AppServices. Then use the AZ-CLI to deploy your apps to the different customer app services. With regards to the different customers: I would start with an AppService per customer within a single App Service Plan, in that way you can limit the costs for now.
We use Azure DevOps build and release pipelines for creating (and updating) App Services and also for building and deploying to these app services. Based on certain conditions we first deploy to Development, after approval gates to Test, QA and finally Production. Nowadays we use YAML pipelines for most tasks, but we started with Azure Portal and AZ-CLI. It takes time to evolve from manual deployment to fully automated.