部署应用程序引擎后存储分段文件 [英] Bucket of Staging files after deploying an app engine

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

问题描述

部署了Google App引擎后,会在Google云存储中至少创建4个存储桶:

After deploying a google app engine, at least 4 buckets are created in the google cloud storage:

  • [project-id] .appspot.com
  • 登台.[project-id] .appspot.com
  • artifacts.[project-id] .appspot.com
  • vm-containers.[project-id] .appspot.com

它们是什么,它们会产生存储成本吗?可以安全删除它们吗?

What are they, and will they incur storage cost? Can they be safely deleted?

推荐答案

我在这里为将来的观众引用相关信息:

I am quoting relevant information here for future viewers:

注意:创建默认存储桶时,您还将获得一个临时存储桶 具有相同的名称,但分期除外.在它之前.你可以 使用此暂存区来存放用于暂存和测试的临时文件 目的;它也有5 GB的限制,但是会自动清空 每周一次.

Note: When you create a default bucket, you also get a staging bucket with the same name except that staging. is prepended to it. You can use this staging bucket for temporary files used for staging and test purposes; it also has a 5 GB limit, but it is automatically emptied on a weekly basis.

因此,从本质上讲,当您创建App Engine Standard或Flexible时,您将获得这两个存储桶.您可以删除存储分区(我删除了暂存分区),并且可以通过运行gcloud beta app repair对其进行恢复.

So in essence, when you create either an app Engine Standard or Flexible, you get these two buckets. You can delete the buckets (I deleted the staging one) and I was able to recover it by running gcloud beta app repair.

这篇关于部署应用程序引擎后存储分段文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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