Refresh deploy docs and contribute.json now that stage deploys from main

未关闭
#487 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 8 天内回复

@stephaniehobson 已经在做这个了。

开始于 2026年11月9日。

评估

这个 Issue 还没有评估数据。

描述

docs/architecture/deploy.md was written on 2026-11-06, before the deploy workflow existed, and a few statements are now stale after the first automated stage deploy (#480, merged 2026-11-09):

  • The "Where the site is served from" table still says stage holds v1.2.0 from 2023-06-14 and that deep links on stage "404 until the first deploy from main". Stage now tracks main; update the table to say so rather than naming a version, and drop the stage caveat from the "Deep links" paragraph.
  • The "How deploys have happened" history can gain the date of the first automated deploy (2026-11-09, commit fdeafe0).
  • public/contribute.json still lists https://data-ensemble.stage.mozaws.net/ as the stage URL. That host is from the AWS era and no longer resolves. Replace it with https://dfc-stage.data-static-websites.nonprod.webservices.mozgcp.net/.

Everything else in deploy.md was re-verified against the Terraform and live headers and still holds. Refs WT-1916.

主要语言
JavaScript
星标
21
派生
7
平均合并
6 天 6 小时
30 天内合并 PR
5

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

mozilla/ensemble 的其他 Issue

查看 mozilla/ensemble 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。