Add "local mode" to support locally defined content in a Labspace#132
Merged
Add "local mode" to support locally defined content in a Labspace#132
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a Labspace starts, it will, by default, clone the content from the content repo. However, there may be situations in which you want to skip this and use locally cloned content, such as running demos.
This PR provides the ability to configure the configurator service with a "local mode" option. In this scenario, there will be no remote git cloning. Instead, the content is mounted into the configurator and then copied into the content volume used in the Labspace.
Example Compose override
This override file will mount the parent directory into the Labspace and use it as the content source