fix: set project workspace in Gitpod VScode

[tyler36]

The Issue

Currently, ddev-gitpod-launch opens Gitpod with "/workspace/ddev-gitpod-launcher" set as the workspace root when using Gitpod VScode.

As a developer, I want the DDEV project as my workspace root.

How This PR Solves The Issue

This PR:

• creates a /workspace/code directory
• clones the target repo into /workspace/code
• defines /workspace/code as the workspace root
• removes some obsolete code

Manual Testing Instructions

• Follow instructions on main page to launch Gitpod session
• Once complete, VSCode Explorer panel should display the "code" folder with the target repo.

Automated Testing Overview

Related Issue Link(s)

Fixes #3

Release/Deployment Notes

[tyler36]

IMO the overall best thing here is to check out the project into its own place in /workspace instead of checking it out into a subdirectory of ddev-gitpod-launcher. Do you think there's a way to do that?

Thats exactly what this PR does. Is it not working as expected?

Oh, I see. The manual steps in the description are wrong.

Manual testing

• Visit https://ddev.github.io/ddev-gitpod-launcher/
• Enter target repo
• Copy the "Link used by "Open in Gitpod" button:" URL
• Replace "https://github.com/ddev/ddev-gitpod-launcher/" with "https://github.com/tyler36/ddev-gitpod-launcher/tree/12-Move-checked-out-code-into-its-own-directory-point-workspace-location" to use the PR instead of main "ddev-gitpod-launcher"

[rfay]

In that case it has nothing to do with vscode does it? I guess that's what confused me. You're doing a good thing for everything and everybody?

[tyler36]

In that case it has nothing to do with vscode does it? I guess that's what confused me. You're doing a good thing for everything and everybody?

Now I am confused. 😄

This PR address an issue from #3 (ddev-gitpod-launcher and selecting VScode as the IDE) specificly the explorer panel. Using d9simple as an example for ddev-gitpod-launcher:

• Current ddev-gitpod-launcher
• PR ddev-gitpod-launcher

[rfay]

IMO it fixes much more than that :) because it fixes the confusion people have by it being in a subdirectory.

[rfay]

Sorry I didn't get back to this today, looking forward to testing it. Great leap forward!

[tyler36]

What a great win!