How Windows users can try gj :: configExplorer standalone

In my previous article introducing gj :: configExplorer I flagged up how an apparent bug in the Windows elements of the Native API for Node.js means it's not currently available to run in VS Code on a Windows desktop. In a comment on that article I offered a workaround, but this requires a Docker-equipped Linux host you can SSH to.

If you don't have a suitable target it's now possible to leverage your local Windows Docker Desktop. Here's how:

1. Open a new VS Code window.

The original steps 2 through 9 can be simplified by running 'Dev Containers: Clone Repository in Container Volume...' from Command Palette and entering 'https://github.com/gjsjohnmurray/gjConfigExplorer.git' at the prompt.

2. Go to Source Control view by clicking on its Activity Bar icon.
3. Click the 'Clone Repository' button.
4. Paste `https://github.com/gjsjohnmurray/gjConfigExplorer.git` into the top-centre prompt and press Enter.
5. Choose a folder in which to create the clone's folder.
6. When prompted, open the cloned repository.
7. Trust the author if prompted.
8. Look for a notification (lower right):
9. Click 'Reopen in Container'. This step may take a few minutes to complete.

The container runs a Linux instance which itself contains Docker, a technique called 'Docker in Docker'.

10. Dismiss the notification about recommended extensions.
11. Wait until the activity of the postCreateCommand from devcontainer.json completes.
12. Switch to Run and Debug view, then click the 'play' button. Or simply press F5.
13. When the Extension Development Host (EDH) window opens, dismiss the notification about being unable to connect to 'iris'.
14. In Explorer view, right-click on the docker-compose.yml file and choose 'Compose Up'.
15. Wait a few minutes for the intersystemsdc/iris-community:latest image to download in the inner (Linux-hosted) Docker. This will provide an IRIS container whose configuration gj :: configExplorer will explore.
16. When the terminal output reports that the container test-iris-1 has started, click on the iris[USER] status bar panel and in the top-centre prompt choose 'Toggle Connection'.

Now click here:

Wait for Structurizr Lite to be started in another container in your Linux container.

Once Structurizr Lite has started you should see a new tab open in your web browser. The page might initially be blank while it downloads resources, but soon you should get this:

A click on the second thumbnail give this:

The 'iris' instance is configured with two ECP data server connections. These are fake because IRIS Community edition's license doesn't include the ECP feature, but luckily this restriction doesn't prevent us defining the connections.

Click on the third thumbnail to get this:

Then use its Zoom button (lower right) plus horizontal scroller to see this:

If you like what you're seeing please support this extension by voting for it in the current DC contest. Voting closes on Sunday 12th October at midnight US Eastern time.