-
Notifications
You must be signed in to change notification settings - Fork 3
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
Server Side Copy #1
Labels
Product Marketing
A tag to indicate that we need to work with our Product marketing team
Uplink
Uplink
Comments
Note from OKR tracking spreadsheet:
|
Week 9 update:
|
Week 11 update:Satellite:
Uplink:
Next Steps:
|
iglesiasbrandon
added
the
Product Marketing
A tag to indicate that we need to work with our Product marketing team
label
Mar 24, 2022
Week 13 update:Satellite:
Uplink:
Next Steps:
|
Week 15 update:
Next Steps:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Product Marketing
A tag to indicate that we need to work with our Product marketing team
Uplink
Uplink
Summary:
Users are unable to copy data within a project or bucket without downloading it and uploading it to the new location.
Pain Point:
Copying data without server-side copy is costly because the user must pay for the download bandwidth.
Intended Outcome
Users will have the ability to copy data from one location to another within a project without having to download and reupload it. This will enable users to move data within their projects and buckets without having to pay for egress bandwidth. This functionality will be added to the library's and CLI tool first and then incorporated into the satellite GUI later.
How will it work?
The technical details of how this functionality will work can be found on the blueprint.
Links:
Storj Milestone: https://github.com/storj/storj/milestone/5
Uplink Milestone: https://github.com/storj/uplink/milestone/1
Blueprint: https://review.dev.storj.io/c/storj/storj/+/5930
Test Plan: storj/storj#4317
The text was updated successfully, but these errors were encountered: