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

Publishing: Enable one-way synchronization #148

Closed
kamil7x opened this Issue Apr 9, 2015 · 8 comments

Comments

Projects
None yet
4 participants
@kamil7x

kamil7x commented Apr 9, 2015

Sometimes, there are situations, when I need to upload all my files to a server, e.g. when switching git branch. But when I try to synchronize, I have notices "remote file was deleted, so delete it locally", but that is not expected action in this case.

I think that possibility of choosing expected behavior could make Publishing better.
For example:

  • force push only (overwriting and deleting remote files, that are not present locally, even if remote files are newer)
  • push only (as above but with possibility to resolve conflicts)
  • standard (as for now, look for newer files and then push/pull them)
  • pull only (same as push only, but in opposite direction)
  • force pull only (same as force pull only, but in opposite direction)

I think this would help not only me, but also other users.

NOTE FROM CAREY: When performing a forced push (all or single file) skip sync analysis

@Naatan Naatan added this to the Backlog milestone Apr 9, 2015

@cgchoffman cgchoffman changed the title from Enable one-way synchronization to Publishing: Enable one-way synchronization Dec 1, 2015

@Naatan Naatan modified the milestones: 10.0, Backlog Mar 17, 2016

@Naatan

This comment has been minimized.

Member

Naatan commented Mar 17, 2016

Let's start with force push and take it from there.

@codermjb

This comment has been minimized.

codermjb commented Mar 17, 2016

I agree with this! Force push will make it much more convenient for us! Thanks!

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Mar 30, 2016

#548 should be noted when this bug is being completed. If the user is going to do a force push and they know they want to then we should not force them to wait for Komodo to do a Sync Analysis of the remote and local directories.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Jun 30, 2016

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Jul 20, 2016

Pull and force pull from Places: Komodo/KomodoIDE@1e3cf2c

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Jul 20, 2016

Allow Override of Sync Action in Publishing Dialog: Komodo/KomodoIDE@35b6019

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Jul 20, 2016

One last thing is to allow "Push/Pull" of a folder from Places. Hitting a nasty bug in the Python code for that. Callback and threading soup. I just found a new clue today though. Multiple Threading.start() calls might be happening on one Threading object, OR two threads are working from the same callback and at somepoint that callback gets invalidated/removed/somethinged.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Aug 9, 2016

I'm going to close this. Any further work we do will be a revamp of the entire tool and not be tracked here, but in a design doc in for a future release.

@cgchoffman cgchoffman closed this Aug 9, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment