v2-platform: 03 R2/S3 storage provider + hardening + dual domains

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
aws, typescript

调研方向

先从 #274 中的 v2 平台服务规范和 #275 中的部署服务核心开始,然后跟踪此处描述的存储适配器接缝。检查 aws4fetch 集成,并将每项验收标准映射到实现或测试位置。完成的标准是 provider 满足上传、配额、流式传输、去重、域名、标头和凭据隔离标准。

由索引模型根据 Issue 内容生成。

描述

ready-for-agent

Parent

#274 (v2 platform services spec)

What to build

The real storage provider: S3-compatible PUTs (aws4fetch) with scoped, service-held tokens behind the storage adapter seam. Explicit content-type map and immutable cache-control on content-hashed paths (the failure mode that stalled the earlier Cloudflare attempt must be impossible). Day-one hardening: streaming (non-buffering) uploads, concurrency cap, per-account size and file-count quotas, MIME allowlist, robots noindex. Two serving domains: the member domain for account-namespaced uploads, the official domain for platform-account CI uploads through the same service — only the service ever holds CDN credentials.

Acceptance criteria

  • Uploaded bundles are fetchable from the member domain with correct content-type and immutable cache-control headers (stylesheets serve as text/css)
  • Re-uploading identical content dedupes (same content-hash path, no duplicate storage)
  • Over-quota, over-count, disallowed-MIME, and concurrent-flood uploads are all rejected cleanly
  • Uploads stream without buffering whole bundles in service memory
  • Official-path uploads land under the platform account on the official domain through the same contract
  • Member-domain responses carry noindex headers
  • Scoped S3 tokens — no account-wide credentials in any plugin environment

Blocked by

  • #275 (deploy service core)
主要语言
TypeScript
星标
5
派生
4
平均合并
9 小时 58 分钟
30 天内合并 PR
212

环境准备

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

从这里开始

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

NEARBuilders/everything-dev 的其他 Issue

查看 NEARBuilders/everything-dev 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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