Ft docs

[oceenachi]

Description

Motivation and Context

This change enables users working with cwlviewer and running the application with docker-compose to be able to connect the application to a java debugger on the local, inspect the containers and debug their application. #319

How Has This Been Tested?

N/A N/A N/A

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x ] My change requires a change to the documentation.
• [x ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[oceenachi]

Hey @mr-c , @tetron, @stain I have raised a PR for the documentation on connecting a java debugger to the cwlviewer application while running with docker-compose. Please review.

[oceenachi]

Hey @mr-c I just figured the images are not showing in this link that you pasted on gitter https://github.com/common-workflow-language/cwlviewer/pull/327/files?short_path=b335630#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5

And I don't really know what to call those buttons for cases where the image doesn't show

[kinow]

I think this can be closed. It's easier to debug it with the IDE locally, starting the DB & Fuseki only with docker compose. The readme contains information about docker compose already, and using that to debug should be straightforward to a Java developer (the IDE steps will vary a bit, but I think we shouldn't document it in our readme).