Add support for dynamic class git repos#159
Merged
Merged
Conversation
The repositories are initialized with a copy of the singularity repo, and a copy of any other repos stored in a new untracked subdirectory `repos` that is similar in function to `docs`. The repositories will be stored in a volume so that persistent changes can be made to them via pushing to them over http from a port on the host.
a945ad7 to
45ee11a
Compare
ef84c65 to
10a6e84
Compare
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.
A new container manages the class git repos.
They are initialized with a copy of singularity and a copy of any other bare repos stored in a new
docslike folder calledrepos, and stored in a volume for persistence.It has a warpdrive like script that allows adding new repos on the fly and runs an http server with a port mapped to the host that can accept pushes to the repos so they can be synced to publish new content as the semester progresses.
CGIT now pulls its repo data from this container's volume in a readonly fashion to publish the repos (behind auth) for students to clone.