-
Notifications
You must be signed in to change notification settings - Fork 11
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
sicksync add
should choose different ports
#56
Comments
So you can actually run two projects simultaneously with |
I haven't tested this yet, but do you mean that syntax actually makes it work? As opposed to doing If so, independence would still be preferable IMO. Sometimes I like to start and stop one sync job while another one keeps running in the background. |
I think we can probably support both cases... I'll revisit this once the modernization effort is through |
This is still an issue. I haven't yet tried the syntax you suggested: And I think starting projects separately should be given more importance, because otherwise you can't start syncing others projects without messing up previously running syncs, or you'd have to start them all again, if I'm understand it correctly. Separate ports might actually be a requirement in that case, as there are going to be separate processes. Although I'm not sure. In the meantime I'm manually making ports different to make my use case work. |
I've tried the single command syntax now: It has problem as I suspected. After starting syncs for two projects this way, and changing a file in one of the projects gets mistaken for that filename in the other project, giving the error like So it seems they do need to be in separate ports? |
sicksync add
chooses the same defaultwebsocketPort
for all projects which causes problems if two projects are run simultaneously (#55). It should choose different ports based on what ports have already been used in other saved projects.The text was updated successfully, but these errors were encountered: