-
Notifications
You must be signed in to change notification settings - Fork 392
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
fix(dvclive): Note on DVC_STUDIO_URL
and DVC_STUDIO_TOKEN
env variablesgit
#5012
Conversation
@@ -15,3 +15,10 @@ os.environ[env.DVCLIVE_OPEN] = "True" | |||
of DVCLive. Defaults to `WARNING`. | |||
- `DVCLIVE_OPEN`: If True, DVCLive will try to automatically open the HTML | |||
generated by `Live.make_report()` in the default browser. Defaults to `False`. | |||
- `DVC_STUDIO_TOKEN`: If set to a valid Studio auth token, and you're running |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: this one overrides the token taken from DVC config. So, when you run it within a repo it's not needed if DVC is connected with Studio, same with VS Code extension.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noted! I'll update the wording on this in a little bit.
I think it's related to #4914. These are technically DVC env vars, not DVCLive. Maybe we need to go ahead and add that finally and link between the pages? @natikgadzhi Is there anywhere else in the dvclive docs you think we need to highlight how to connect to Studio? |
Closing as stale + it's absorbed by #5030 |
Summary
Just noticed we have the env vars page for DVCLive, but it did not list the studio url and studio token vars. Added them to the list, and added the link to live tracking page in the Studio section.