-
Notifications
You must be signed in to change notification settings - Fork 494
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
Administration Changes to Support rsync #3347
Comments
During the 2016-09-08 SBGrid Sprint Planning meeting ( https://docs.google.com/document/d/1wWSdKUOGA1L7UqFsgF3aOs8_9uyjnVpsPAxk7FObOOI/edit ) this issue was given an effort level of "3" because code has already been written. We're using With regard to administrators being able to define the file transfers available we have defined an enum called |
@bmckinney @djbrooke and I discussed this and we moved it to "Ready" at https://waffle.io/IQSS/dataverse @bmckinney and I are fine with the approach so I believe the next step is to make a pull request based on the code mentioned above. |
|
@djbrooke this issue is one of eight created last September in our attempt to break #3145 into smaller chunks: #3145 (comment) Yes, the code mentioned above is helpful, especially #3724. There's still an open question of if @scolapasta wants to weight in on the approach before we commit to it, as mentioned at #3347 (comment) . In #3724 this is described as "Binary configuration items (on/off switch), or lists (native/http,dcm/rsync+ssh, etc)? Additional implementation complexity and/or performance of lists vs binary hasn't been evaluated." A decision still needs to be made. For now I'll link to this issue from #3724. |
#3348 is still open as well so we can circle back to anything written back above, if necessary. |
We'll need to make changes at the Installation and the dataverse level to support the new options available for rsync. Two that were discussed were:
The text was updated successfully, but these errors were encountered: