-
Notifications
You must be signed in to change notification settings - Fork 394
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
Change S3 bucket from old dvc-share
to new dvc-public/{prefix}
#560
Labels
p1-important
Active priorities to deal within next sprints
website: eng-doc
DEPRECATED JS engine for /doc
Comments
Also found that
|
shcheklein
added
🐛 type: bug
Something isn't working.
p1-important
Active priorities to deal within next sprints
labels
Aug 15, 2019
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
jorgeorpinel
added a commit
that referenced
this issue
Aug 15, 2019
…/remote and and misc doc improvements. Per #560
jorgeorpinel
added a commit
that referenced
this issue
Aug 15, 2019
jorgeorpinel
added a commit
that referenced
this issue
Aug 15, 2019
jorgeorpinel
changed the title
change S3 bucket from old
Change S3 bucket from old Mar 16, 2023
dvc-share
to new dvc-public/{prefix}
dvc-share
to new dvc-public/{prefix}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
p1-important
Active priorities to deal within next sprints
website: eng-doc
DEPRECATED JS engine for /doc
We decided to migrate from an old S3 bucket
dvc-share
to use certain prefixes (folders) in a newdvc-public
bucket for use in documentation. The prefixes identified now are:code
: For example code archivesdata
: For sample datasetsremote
: For using as an S3 remote (read-only in examples)The main use for the bucket is to
wget
(download) files or use as DVC remote (read-only) in the examples throughout command references and Get Started section (as well as in https://dvc.org/doc/commands-reference/get/url) but there are other uses.Spanned from #487
The text was updated successfully, but these errors were encountered: