Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Custom Certificates

未關閉
#7,319 0 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
45/100
Issue 類型
文件
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
ubuntu
領域
documentation

研究方向

找出涵蓋自訂憑證的文件區段,並檢視其中如何搭配 config.yaml 範例描述 cert 和 cert-key。釐清必須編輯 config.yaml,且 cert 指向的是憑證檔案路徑,而不是布林值,接著根據現有命令和 mkcert 指引核對措辭。

由索引模型根據 Issue 內容生成。

描述

docs

What is your suggestion?

Within the documentation, it mentions that the below to add your own cert:

# Replaces "cert: false" with "cert: true" in the code-server config.
sed -i.bak 's/cert: false/cert: true/' ~/.config/code-server/config.yaml
# Replaces "bind-addr: 127.0.0.1:8080" with "bind-addr: 0.0.0.0:443" in the code-server config.
sed -i.bak 's/bind-addr: 127.0.0.1:8080/bind-addr: 0.0.0.0:443/' ~/.config/code-server/config.yaml
# Allows code-server to listen on port 443.
sudo setcap cap_net_bind_service=+ep /usr/lib/code-server/lib/node

It finishes with the final statement regarding the cert and cert-key config fields.

If you'd like to avoid the warnings displayed by code-server when using a self-signed certificate, you can use [mkcert](https://mkcert.dev/) to create a self-signed certificate that's trusted by your operating system, then pass the certificate to code-server via the cert and cert-key config fields.

Issue: when installing via ubuntu to change the config.yaml file, the docs just mentions to pass in the fields which I understand to modify the config.yaml file but its not clear. Nor does it state that the cert:true field should ACTUALLY be changes to the directory of the .pem/.crt file not a boolean value.

How will this improve the docs?

This will clearly state that the config.yaml file should be modified and to pass in the directory of the your-cert.pem file into the cert field instead of a boolean value

Are you interested in submitting a PR for this?

Sure!

主要語言
TypeScript
星號
79.5k
分支
6.9k
平均合併
1 天 15 小時
30 天內合併 PR
37

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

coder/code-server 的其他 Issue

查看 coder/code-server 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。