With the addition of the display option for containers (web or terminal), the @lab.container.Terminal replacement token needs some updates, in my opinion.
Currently, the replacement token inserts whatever display option is set at the container level. So if the container is set to display web, the Terminal token displays the web page, not a terminal.
It would be better to have two commands, @lab.container.terminal and @lab.container.website, so that lab developers can choose which interface to embed in the instructions.
| Who would most benefit from this idea? | Lab Developers or Lab Authors |
|
What is the problem you are trying to solve?
With two separate commands that operate independently of the default display option for the container, lab developers could use "web" as the main option (appearing in the big window) and then embed the terminal where necessary in the instructions for brief access. Right now, there's no way to give students (or lab developers, for that matter) access to a terminal on the container if the container is set to display web. |
|
Thanks for taking a minute to send along this suggestion! Our Product Group has given this an initial review and assigned this a status of "Future Consideration." This status mean this Idea is not yet on our roadmap, but will be part of our normal prioritization processes.
If you have additional context or would like to generate more demand, feel free to edit your original post, add a comment, and/or invite your peers to upvote your Idea.
