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

Identical file structures on different servers causes problems editing files #4989

cyberduck opened this issue Jul 7, 2010 · 2 comments


Copy link

cyberduck commented Jul 7, 2010

a052a5d created the issue

I've got two servers, a development server and a production server with near-identical file structures. If I want to edit the same file on the dev server and the production server simultaneously - for instance, to partially implement new code - Cyberduck won't open both files simultaneously in TextMate. Instead, editing one file instantly overwrites the old one. Files should be differentiated by a unique server ID such as the IP address rather than whatever is currently differentiating them.

Steps to replicate:

  1. Set up two SFTP servers with the same username/password and file structure.
  2. Login to both in separate Cyberduck windows.
  3. Open a file on one server in TextMate.
  4. Open the same file on the other server. Only one TextMate window is open, containing the file from the second server.

Here's where it gets especially nasty: the connections sometimes get confused as to who last opened the file. If I do this by accident without realising, sometimes the data on the dev server - new code - gets overwritten with data from the production server. I've accidentally erased work because I've saved a file that was opened from the production server and Cyberduck has overwritten the file on the dev server.

Copy link
Collaborator Author

cyberduck commented Jul 12, 2010

@dkocher commented

In dc3e0af.

Copy link
Collaborator Author

cyberduck commented Jul 22, 2010

@dkocher commented

#4505 closed as duplicate.

@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.
None yet

No branches or pull requests

2 participants