We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For now tljh-repo2docker can build environments from repositories that are publicly accessible.
tljh-repo2docker
However it would be useful if it could also build environments from private repositories.
BinderHub supports this use case with the git_credentials option.
git_credentials
The value is then passed as a GIT_CREDENTIAL_ENV environment variable to the builder (the jupyter/repo2docker:master Docker image): https://github.com/jupyterhub/binderhub/blob/3cb82fafa55d25e8fb6c6559423ffdef57919aa3/binderhub/build.py#L236
GIT_CREDENTIAL_ENV
jupyter/repo2docker:master
For tljh-repo2docker, we would need to pass these credentials using the GIT_CREDENTIAL_ENV environment variable to the command here:
tljh-repo2docker/tljh_repo2docker/docker.py
Lines 82 to 96 in 05ce3d5
Something like the following:
cmd = [ "GIT_CREDENTIAL_ENV=username=foo\npassword=bar", "jupyter-repo2docker", "--ref", ref, "--user-name", "jovyan", "--user-id", "1100", "--no-run", "--image-name", image_name, "--appendix", "\n".join(labels), repo, ]
The credentials could be specified in the form:
Or as a configurable for the tljh_repo2docker plugin.
tljh_repo2docker
The text was updated successfully, but these errors were encountered:
Documentation to access private repositories for BinderHub:
https://binderhub.readthedocs.io/en/latest/zero-to-binderhub/setup-binderhub.html?accessing-private-repositories#accessing-private-repositories
The token can be generated from the GitLab UI:
Sorry, something went wrong.
And I guess similar things could be done with the GitHub UI:
Optional extra git credentials could be in a <detail> section of the form.
<detail>
There could be an option to fill the password with the hub authentication token for the case where we use the gitlab's SSO.
Successfully merging a pull request may close this issue.
For now
tljh-repo2docker
can build environments from repositories that are publicly accessible.However it would be useful if it could also build environments from private repositories.
BinderHub supports this use case with the
git_credentials
option.The value is then passed as a
GIT_CREDENTIAL_ENV
environment variable to the builder (thejupyter/repo2docker:master
Docker image): https://github.com/jupyterhub/binderhub/blob/3cb82fafa55d25e8fb6c6559423ffdef57919aa3/binderhub/build.py#L236For
tljh-repo2docker
, we would need to pass these credentials using theGIT_CREDENTIAL_ENV
environment variable to the command here:tljh-repo2docker/tljh_repo2docker/docker.py
Lines 82 to 96 in 05ce3d5
Something like the following:
The credentials could be specified in the form:
Or as a configurable for the
tljh_repo2docker
plugin.The text was updated successfully, but these errors were encountered: