Explain how two people on different machines try reciprocal practice before staging
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 88/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- cloud, github, rust, sqlite
调研方向
从 docs/peer-interviews.md 中现有的验收检查开始，添加一条简短说明，介绍如何在 staging 前尝试互助练习。解释为什么 localhost 和 LAN 地址无法让远程伙伴访问麦克风，以及为什么双方需要使用同一个服务器和 lobby。说明双方必须共用 HTTPS origin，且 OAuth callback 必须匹配；可以将隧道作为可选示例，并注明任何拥有其 URL 的人都能访问暴露出来的服务器。
由索引模型根据 Issue 内容生成。
描述
docs/peer-interviews.md assumes a staging deployment: its acceptance check uses "two real GitHub accounts in separate browser profiles, headphones and a staging deployment". It does not say how two people on different machines try reciprocal practice when the server runs on one person's computer, which is what a teaching assistant or a contributor does first. Three things each cost us time while doing so (at 5e00eab):
127.0.0.1:3000is reachable only from the machine running the server. A partner who opens the same address reaches their own machine.- Binding to a LAN address and opening
http://192.168.x.x:3000loads the page, but the browser does not expose the microphone outside a secure context (HTTPS or localhost), so the room has no audio. - Two people each running their own server with the same LiveKit credentials do not see each other in Available partners. Pairing lives in each server's SQLite ("HTTP and SQLite own membership, roles, clocks, snapshots and feedback"), so sharing a LiveKit project does not share the lobby.
What worked: one person runs the server, exposes it over HTTPS with cloudflared tunnel --url http://127.0.0.1:3000, sets the OAuth App's callback to the tunnel origin plus /api/callback, and both people open the tunnel's /peer-lobby and sign in with different GitHub accounts.
Intended correction: a short "Trying it with a partner before staging" note in docs/peer-interviews.md that states the three constraints above and the requirement that both people use one server over HTTPS. It does not need to endorse a particular tunnel; naming one as an example, with the caution that it exposes the server and its provider quotas to anyone holding the URL, is enough.
Reader outcome: someone with a working local server knows, before inviting a partner, that they need one shared HTTPS origin and a matching OAuth callback.
Related: the OAuth App setup steps are #645 and the single-redirect-URI behavior is #643; this issue is only about reaching one server from two machines.
- 主要语言
- Rust
- 星标
- 228
- 派生
- 150
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 230
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
sysprog21/codetrial 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
sysprog21/codetrial#645 · 1 条评论 ·
维护者通常 1 天内回复
-
Show recorded scores in past attempt rows可能已有人在做 @liehcheng 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
sysprog21/codetrial#604 · 4 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Calibration can pass invalid assessability data可能已有人在做 @Jonathas2127 今天认领。 未关闭
sysprog21/codetrial#649 · 已指派 1 人 ·
维护者通常 1 天内回复
-
A failed GitHub sign-in shows only a JSON error可能已有人在做 @Ray891220 今天认领。 未关闭
sysprog21/codetrial#644 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 55/100
sysprog21/codetrial#643 · 1 条评论 ·
维护者通常 1 天内回复
查看 sysprog21/codetrial 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
software-mansion/pathfinder#3620 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
bug priority: low
难度 1/5 1 小时以内 新手友好度 90/100
storytold/wordcraft#6211 · 1 条评论 ·
维护者通常 2 天内回复
-
backlog multiple issues priority: low
难度 2/5 1-3 小时 新手友好度 72/100
storytold/pdfcraft#6911 · 2 条评论 ·
维护者通常 2 天内回复
-
DGNIMPORT: "The DGN model has nothing that can be imported" when the first element streams are empty未关闭
难度 2/5 1-3 小时 新手友好度 76/100
HakanSeven12/OpenCADStudio#2820 · 1 条评论 ·
维护者通常 1 天内回复