-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically install JetBrains IDE plugins listed in devcontainer.json #1153
Comments
Hi @dubinsky, I'm with you there, DevPod should install these plugins automatically. Jetbrains is actively working on the details of their customization (#1, #2). For the time being I'd attempt to install the plugins under the |
Here, I am talking only about plugins, so this would be excellent if the ones listed under Thank you!! |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 60 days with no activity. |
Is your feature request related to a problem?
Yes: one of the advantages of using
devpod
anddevcontainers
is the ability to spin up pre-configured development environment for a repository; right now, while VSCode extensions needed can be described in thedevcontainer.json
file and installed automatically, JetBrains IDE plugins can not.Which solution do you suggest?
After installing a JetBrains IDE, automatically install plugins listed in pre-determined location in the
devcontainer.json
file, for example:Which alternative solutions exist?
None that I know; my current work-around is:
Create a workspace, but do not start the IDE:
Run the following script supplying the workspace name on the command line:
(see: https://www.jetbrains.com/help/idea/work-inside-remote-project.html#plugins)
The command works, but results in:
Start remote development in the workspace:
Additional context
Right now, after spinning up a workspace with code in - say - Scala with IntelliJ Idea, developer will either have to manually install the Scala plugin using the IDE's UI and restart the IDE or split the spin-up into three stages as in the work-around described above. Both approaches go against the spirit of
devpod
: start a fully configured development environment with one command (or one click); both require from the developer some additional actions and (even worse!) put on the developer some additional cognitive load needed to understand what those actions are.Instead, all the actions required to obtain a working development environment should be automated and the decision what those actions are should reside in the code repository itself (side-by-side with the information on what tools have to be installed in the development environment).
It is true that the choice of the IDE to use belongs to the developer spinning up the workspace, but what plugins must be installed into the IDE chosen by the developer for it to be able to work with the code belong in the code.
As far as I understand, extensions to install in VSCode can indeed be listed in the
devcontainer.json
file; the same capability should exist for IntelliJ Idea.Thank you!
P.S. There are some plugins that developer uses to customize the IDE (themes etc.); decision which plugins of this nature to install, regardless of the code repository underlying the workspace, does reside with the developer, and a facility to configure such plugins/extensions for automatic installation per IDE should be provided also (something like
devpod ide set-options intellij -oPLUGINS="..."
).The text was updated successfully, but these errors were encountered: