Skip to content

support for safer operation with more than one developer #73

@w-barath

Description

@w-barath

It's great. Coming from netbeans which is spectacularly slow and unreliable for remote editing, this is a godsend.

Beware: syncing folders is destructive. If you sync remote to local it won't sync only the differences - it will obliterate any new local files. Same thing vice-versa. This can bite you in the ass in several subtle ways:

If you add 10 files to /media with gimp and then want to sync them to remote, you must do them one at a time or you risk obliterating remote files/folders which you don't have locally.

If you create a new local folder which happens to exist remotely and you add 2 files to it, everything goes smoothly until you sync the folder, then boom.

If you work in a folder shared with another developer and they add a file, subfolder etc to a folder you're working in and you sync your folder to the server, their uploads are consigned to oblivion.

If you work with another developer and they obliterate your files/folders, and then you sync remote to local to get their work, boom you lose your own local copies! Ouch! Hopefully you are using VCS or fine-grained differential backups of your projects so you can recover!

I propose that there should be 2 folder sync options: the default (sync newer) should only copy newer files from src to dst, and the other (sync all and delete) should behave as the current folder sync does. That would allow this lovely tool to be used safely in a shared work environment, or by normal mortals who can make mistakes ;-)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions