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

VEDA Docs in instances doesn't update #62

Open
wildintellect opened this issue Jan 9, 2025 · 1 comment
Open

VEDA Docs in instances doesn't update #62

wildintellect opened this issue Jan 9, 2025 · 1 comment

Comments

@wildintellect
Copy link

wildintellect commented Jan 9, 2025

The version of VEDA Docs cloned to users home directories doesn't update automatically. So it stays at whatever version was cloned at the time you launched your first Pangeo instance.

We either need to document this so users know they have to git pull if they want the latest docs, or we need a mechanism to refresh somehow.

Not Critical but something to think about.

cc: @yuvipanda @sunu @j08lue

@j08lue j08lue transferred this issue from NASA-IMPACT/veda-docs Jan 9, 2025
@j08lue
Copy link
Collaborator

j08lue commented Jan 9, 2025

Took the liberty to transfer this issue here to JupyterHub.

I second the goal that users always have the latest veda-docs available in their container.

git pull will fail if users made changes in their copt of veda-docs that conflict with new upstream commits, or checked out another branch.

Ideally, the veda-docs copy included with the container would be read-only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants