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

Feature Request: Support for bi-directional syncing #8

Open
duro opened this issue Dec 16, 2014 · 2 comments
Open

Feature Request: Support for bi-directional syncing #8

duro opened this issue Dec 16, 2014 · 2 comments

Comments

@duro
Copy link

duro commented Dec 16, 2014

Right now sicksync is one-way. It pushes files from the local to the remote. In some development cases the need for bi-directional syncing is needed.

Justification:

Doing NPM installs on a local (OS X) that is a different architecture than the remote (Linux) is a bad idea, since modules that have native extensions require being compiled on the arch where they will be ran. I am often SSH'd into the remote during development and will perform my npm install MODULE --save there. This updates the package.json. That update should be mirrored back to the local to be committed into source control.

@laggingreflex
Copy link
Contributor

laggingreflex commented Oct 11, 2016

+1. Was this implemented in v1.2.0?

@joelgriffith
Copy link
Contributor

This never was implemented... and might require some heavy re-writing, so going to re-label this.

@joelgriffith joelgriffith removed this from the v1.2.0 milestone Oct 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants