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

Transfer bookmarks #7943

Closed
cyberduck opened this issue May 7, 2014 · 4 comments
Closed

Transfer bookmarks #7943

cyberduck opened this issue May 7, 2014 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 7, 2014

023e870 created the issue

Hello,

For peoples that heavily often do same transfers/sync between folders, it could be useful if those kind of jobs could be saved. Maybe a good idea would be to place those jobs as sub bookmarks in the corresponding connection bookmark. Sub bookmarks would be accessed by clicking on a new button that could be placed on the right side of the connection bookmarks.

A sub bookmark item would be composed by :

  • the job type (upload / download / sync)
  • job options, depending of the job type : resume/overwrite/rename/skip/compare for upload and download ; download/upload/mirror for sync
  • the source folder
  • the destination folder

This will simplify a lot repetitive tasks and will be a gain of time.
Any comments are welcome.

Thanks !

Cédric

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 8, 2014

@dkocher commented

You can always restart a transfer by choosing Reload in the Transfers window. It will prompt again for the action if a file already exists, though.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 12, 2014

023e870 commented

Replying to [comment:1 dkocher]:

You can always restart a transfer by choosing Reload in the Transfers window. It will prompt again for the action if a file already exists, though.

Yes I totally agree, and its really helpful. My thoughts are cases where CyberDuck is mainly used for sync operations / backup purposes, running tasks from the history is not the cleanest way, plus the history list only show the folder name and could lead to mistakes.

A future vision would be, when jobs will be implemented, to allow a kind of jobs scheduling like "run this sync jobs every 1 hour", I agree that such features tends more to the backup solution than a transfer client, but a the end what's the difference ? both cases need to transfers files between differents places.

Cheers

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 16, 2014

@dkocher commented

Periodic background tasks is not something we are eager to implement. But the display of transfer items also relates to #6294.

Loading

@cyberduck cyberduck closed this May 16, 2014
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 20, 2014

023e870 commented

Hello David,

Too bad for the periodic background tasks ;-)
Indeed, request #6294 seems great and looks like a bit what I am looking for.

Cheers !

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants