While integrating Workshop with a few projects, I found myself in situations where I would have liked to be able to do something like workshop <workshop-name> <custom-command> as a shorthand/alias of a custom script that executes on the host and not in the container. The command would be something that acts/interacts with the specific containers.
The goal would be portability, so everything can be packaged into an SDK, without having to distribute separately the scripts/tools that run on the host and that interact with the particular workshop.
I haven't found a simple way to do this when studying the documentation.
While integrating Workshop with a few projects, I found myself in situations where I would have liked to be able to do something like
workshop <workshop-name> <custom-command>as a shorthand/alias of a custom script that executes on the host and not in the container. The command would be something that acts/interacts with the specific containers.The goal would be portability, so everything can be packaged into an SDK, without having to distribute separately the scripts/tools that run on the host and that interact with the particular workshop.
I haven't found a simple way to do this when studying the documentation.