Skip to content
New issue

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

[DOC] - git repo auto-deploy explanation and examples #437

Closed
1 task done
kcpevey opened this issue Apr 30, 2024 · 4 comments · Fixed by #479
Closed
1 task done

[DOC] - git repo auto-deploy explanation and examples #437

kcpevey opened this issue Apr 30, 2024 · 4 comments · Fixed by #479

Comments

@kcpevey
Copy link
Contributor

kcpevey commented Apr 30, 2024

Preliminary Checks

Summary

We've added a mechanism to provide all users with a copy of any git repo but it has not yet been documented (or if it is, make it more findable)

This is defined in nebari-config.yml and checked when the user server is started.

Steps to Resolve this Issue

...

@kcpevey
Copy link
Contributor Author

kcpevey commented Apr 30, 2024

Should probably go in https://www.nebari.dev/docs/explanations/advanced-configuration/

Edit: See the comment below

@pavithraes
Copy link
Member

We have some docs here: https://www.nebari.dev/docs/explanations/custom-overrides-configuration#jupyterlab

We need to add a little more descriptive text to ensure this shows up on common search terms

@kcpevey kcpevey added this to the Documentation Burndown milestone Apr 30, 2024
@pavithraes
Copy link
Member

xref: #401

@kcpevey
Copy link
Contributor Author

kcpevey commented May 1, 2024

All the references in the docs call it "initial_repositories" which I did not think to use as a search term when I was trying to find this feature in the docs. I was trying terms like git repo and auto-deploy which also don't seem like great names, but its all I could think of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done 💪🏾
Development

Successfully merging a pull request may close this issue.

2 participants