You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: