安全部署GAE应用程序 [英] Safe deployment of GAE apps

查看:111
本文介绍了安全部署GAE应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想确保当我更新我的GAE网站时,它对当前正在使用我的网站的用户没有任何不良影响。



Google自动使这个过程安全,例如通过:


  • 完成所有待处理的请求

  • 暂时延迟新请求

  • 更新代码

  • 处理新请求



运行并更新服务器代码?



如果后者有任何建议做安全更新?任何其他预防措施的队列中的任务?

解决方案

我认为对于一些(通常很短)的时间,并排侧。所以一些请求是在新版本上,但有些仍然在旧版本上完成。



偶尔,我在部署时收到少量用户的错误。



我认为最安全的方法是部署到不是活动版本的新版本,然后在管理控制台中更改默认的'版本'。这确保了最快,最干净的转换。


I want to make sure that when I update my GAE site that it does not have any bad side effects for users who are currently using my site.

Does Google automatically make this a safe process, e.g. by:

  • complete all pending requests
  • temporarily delay new requests
  • update code
  • process new requests

Or does Google just terminate whatever is running and update the server code?

If the latter, any recommendations for doing a safe update? Any other precautions for tasks in queues?

解决方案

I think that for some (usually quite short) time, your two versions are serving side-by-side. So some requests are on the new version, but some are still finishing up on the old version. Be sure to consider that when thinking about how your data structures will update.

Occasionally, I have received errors from a small number of users while deploying.

I think the safest way to do it is to deploy to a new 'version' that isn't the active one, then to change your default 'version' in the admin console. This ensures the quickest, cleanest, changeover.

这篇关于安全部署GAE应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆