coder / coder/code-server

[Feat]: Ability to set proxied ports to public

オープン
#6,008 コメント 1 件 リアクション 8 件 担当者 0 名 GitHub で見る
enhancement
主要言語
TypeScript
スター
79.3k
フォーク
6.8k
平均マージ
2日 6時間
マージ済み PR(30日)
41

説明

## What is your suggestion?

Set proxied port visibility to either public or private. When a port is set to public, cookie-based authentication is disabled, even if the auth is set to password.

In GitHub Codespaces, the feature looks like this:

![image](https://user-images.githubusercontent.com/37142182/217548692-e58bdc52-f8fa-4817-b814-f0920aafc3b1.png)

## Why do you want this feature?

Useful for developing with 3rd party integrations that call your API (e.g. webhooks, Slack or Discord bots)

## Are there any workarounds to get this functionality today?

What I currently do is I turn off authentication in code-server, then I do authentication at the reverse proxy level instead, which lets me turn off authentication based on paths. So all paths that match the specified proxy are not authenticated.

This works but is not amazing because either all ports are public or all ports are private; I can't mix the two.

## Are you interested in submitting a PR for this?

Not really, the workaround is acceptable for my current use-case

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。