Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Using Insiders/EAP versions of IDEs #8207

Closed
@matifali

Description

@matifali

Context

Previously, VS Code insiders could be used with Coder workspaces in 2 ways.

  1. Runningcoder config-ssh and then usingVS Code Remote SSH extension.
  2. UsingCoder Remote VS Code extension

These two methods allow using VS Code Desktop Insiders, but the "VS Code Desktop" button couldn't be used due to the different URI used in both versions.

  1. This was addressed by adding a dropdown infeat: add support for insiders channel to "VS Code Desktop" button #7730 that allows directly launching VS Code Insiders from the dashboard button.
    image

Problem

  1. Some templates have no use of "VS Code Desktop" or "VS Code Insiders Buttons" as they are best suited for another IDE or virtual desktop. e.g., MATLAB or data science templates that use Jupyter Notebook/Lab.Remove VS Code Insiders hard-coded icon and make it site-wide optional #8032
  2. Some enterprises do not allow insider/EAP/beta versions of an IDE (Methods 1 and 2 can still be used unless they block SSH access.
  3. If a developer/user wants to use the insiders version, they can use options 1 and 2, but option 3 will not work if there is no VS code Insiders button.

Possible Solutions

  1. Make helper apps optional (e.g. “VS Code Desktop”) #8033 discusses a possible solution that allows controlling the dashboard buttons on the template's scope and can address problem 1 when an IDE is irrelevant to a template.
  2. To solve problem 3, we can have a setting (check box)
    ☑️ Use beta versions of IDEs
    (under settings -> account -> preferences)
    that changes the VS Code Button to VS Code Insiders button if checked. It should be disableable deployment-wide so that devs can't use the insiders version from the dashboard. (They can still use methods 1 and 2 unless SSH access is disabled).

cc:@bpmct

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp