Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[REQUEST] Update Documentation about RELAY_PRIVATE_KEY

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

维护者通常 1 天内回复

@cameri 已经在做这个了。

开始于 2023年2月16日。

评估

这个 Issue 还没有评估数据。

描述

enhancement

Is your feature request related to a problem? Please describe.
It is unclear how to configure a paid relay so that it sends out the PNs with the invoice.

Describe the solution you'd like
Update documentation accordingly.

Describe alternatives you've considered
Without documentation I have tried the following. This might help to see what I was understanding based on the existing documentation:

  • I set a secret in docker-compose.yml (and I can read it using docker exec <container-id> printenv SECRET)
  • I assumed that a private key is generated automatically, because RELAY_PRIVATE_KEY default value is (auto-generated), however docker exec <container-id> printenv RELAY_PRIVATE_KEY returns nothing.
  • Next assumption was that I might have to create a keypair myself, which seems to be the solution, but it is not obvious!

Thanks!

主要语言
TypeScript
星标
829
派生
234
平均合并
2 天 10 小时
30 天内合并 PR
24

环境准备

从这里开始

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

cameri/nostream 的其他 Issue

查看 cameri/nostream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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