canonical / canonical/workshop

Ability to extend Workshop via a plugin system

Open
#761 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
108
Forks
17
Avg merge
1d 7h
Merged PRs (30d)
40

Description

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 ` 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.