feat!: move legacy build out to a plugin #40
Draft
Conversation
This file contains 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
kdmccormick
changed the title
kdmccormick
force-pushed
the
kdmccormick/legacyfrontends
branch
from
34a2628
to
0fe8470
Compare
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.
Moves legacy frontends to a new plugin: https://github.com/kdmccormick/tutor-legacyfrontends (the interesting lines: https://github.com/kdmccormick/tutor-legacyfrontends/blob/master/tutorlegacyfrontends/plugin.py#L14-L55)
This plugin would be enabled by default, but developers could disable it in order to seriously speed up their image builds.