Red Hat OpenShift Dev Spaces

[@MikeEovino-s2o]

Great info! Thanks for sharing this.

[@BrandYourself-ey6er]

If you have 3 repos. Are you able to run each repo in the same workspace? For example if you are working on multiple applications

[@CloudNativeDevelopment]

Great question! You absolutely can. The way to accomplish this is by just adding multiple attributes under the projects section, you can see an example in the Random Thoughts repo from the video here: github.com/cgruver/che-demo-app/blob/main/devfile.yaml#L6 or if you prefer the devfile docs: devfile.io/docs/2.2.1/adding-projects , just scroll down to the "A devfile with multiple projects section". One thing to note, by default only the first project listed will show in the editor when the workspace starts up. There are 2 options to fix this. First, you can manually add the folder through the editor, by default all projects are cloned into the "/projects" directory. The other option is to automate! You can create a code-workspace, Random Thoughts example: github.com/cgruver/che-demo-app/blob/main/che-demo.code-workspace#L2 , file to define your settings and store it in one of the git repos for your project, my preference is the one the devfile lives in, from there you can either manually load it once with the workspace starts by selecting it in the editor, or for extra style points add an env variable in your devfile to load it automatically, for an example of that check this: github.com/NateLove/quarkus-kafka/blob/main/devfile.yaml#L11 .

[@kuyokuSan]

sudo passw?

[@CloudNativeDevelopment]

Sorry, but I am not sure I understand the question... Could you clarify?

[@kuyokuSan]

​@@CloudNativeDevelopment how to get sudo?

[@CloudNativeDevelopment]

@@kuyokuSanYou wouldn't give users of DevSpaces super-user access. It would be an anti-pattern and would not provide any significant value to the users. Could it be done? Perhaps. I would recommend against it as it provides too many possible exploitation possibilities. It would help if you were to explain why you want to grant superuser privileges.

[@mervenazmumcu8096]

@@CloudNativeDevelopment Hello, I want to upgrade my Go version, so I plan to remove the old version and add the latest Go version to my PATH. But do I need to be root for this? How can I upgrade my Go version?

[@CloudNativeDevelopment]

@@mervenazmumcu8096 you would need to rebuild the Dev Spaces base image... There should be newer based images released and in the registry on a regular basis, so you should be able to update your DevFile to point to the newer image with the newer version of Go.

[@jorgeadrian93]

How do you configure to automatically run the workspace on startup? At minute 15:35 the workspace changes to /?workspace=/projects/che-demo-app/che-demo.code-workspace

[@CloudNativeDevelopment]

Great question, there is an environment variable you can define in your define to apply a default code workspace config. The variable is VSCODE_DEFAULT_WORKSPACE, and you can see an example of that here: github.com/NateLove/quarkus-kafka/blob/main/devfile.yaml#L11

[@jorgeadrian93]

​@@CloudNativeDevelopment That's awesome! Thanks for the quick reply. I updated my devfile, committed and pushed to the fork and I noticed that I need to delete the current workspace and load it again. Do you know if there is any way to reload the latest version of the devfile without creating a workspace from scratch?

[@CloudNativeDevelopment]

@@jorgeadrian93 Another great question. As of version 3.7 I believe of the operator they added an option to restart from local devfile. If you click on the button in the lower left where it says Dev Spaces, that should open the menu and give you the option to restart from there. Word of caution though, before doing this make sure to push any code changes, if you accidentally make a change to the devfile that can break the workspace it can be tough to recover.

[@jorgeadrian93]

@@CloudNativeDevelopment Very neat ... thanks for sharing 😁Where do you get those tips and tricks? I don't see them in the documentation.

[@CloudNativeDevelopment]

@@jorgeadrian93 well I've been fortunate to be able to work directly with the engineering team, so I've learned a lot from them. I will say they do try to announce the new features with the release notes so I did find the workspace info there access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.7/html/release_notes_and_known_issues/new-features#enhancement-crw-4531, but it's a newer feature so it may take some time for it to make it to the official docs.