Add support for devcontainers #73
Conversation
Devcontainers make it very easy for project to distribute the working development environment to their developers using VSCode. This adds support for devcontainer, including the Github action. The workflow is as following: - With every new version of the container, go to the GitHub actions, pick the "Build and publish devcontainer", and trigger the workflow action with the new version as parameter - Add the version to the devcontainer template, so that users can pick it, also update the version of template so it gets published (just increment the patch version), then trigger the workflow "Release devcontainer template"
|
Not sure if you want this. It also does not need to reside in this repo, but can be easily maintained outside. You can just try it out by replacing iic-jku with wallento in the devcontainer template URL. Add to an existing project: https://youtu.be/Mqqgis5QrbU If this devcontainer is found in a project repo, this is the workflow: https://youtu.be/SGQzJ-WOaGI As a bonus, it comes with Surfer support already via its VSCode plugin ,) |
|
Also, to note this is just quickly spinning it up and using a bit in my own projects, its not fully tested and further need might be needed. The extra image is needed because devcontainer requires the user to exist, while there seems to be a necessity to have nss_wrapper. Maybe its an option to already have the user in passwd? But I assume it has a very good reason why you handle it that way. |
|
@MrHighVoltage This looks like a good thing to add. Can you please take a look if anything else needs to be modified, or whether we can merge the changes as-is? |
hpretl
requested review from
MrHighVoltage and
hpretl
and removed request for
hpretl
|
Merged this PR into |
Devcontainers make it very easy for project to distribute the working development environment to their developers using VSCode.
This adds support for devcontainer, including the Github action.
The workflow is as following:
With every new version of the container, go to the GitHub actions, pick the "Build and publish devcontainer", and trigger the workflow action with the new version as parameter
Add the version to the devcontainer template, so that users can pick it, also update the version of template so it gets published (just increment the patch version), then trigger the workflow "Release devcontainer template"