-
Notifications
You must be signed in to change notification settings - Fork 32
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
Implement an rsync receiver, too #9
Comments
d5a5b3d lays the foundation. Next up is actually writing files to disk. |
d1c307d writes files to disk. Next up is generating checksums / transferring deltas |
@stapelberg Is this ready to go yet? This would be great for my backup/restore functionality 😅 I'm happy to help test your work! |
The status in the commit messages and first comment of this issue is accurate. A receiver exists (so feel free to try it out!), but it doesn’t map user/group ids/names across machines. |
@stapelberg Thanks! I actually did, however I decided to go with a completely different solution as I wasn't able to get what I had hoped working with |
Yes, the daemon doesn’t accept uploads yet. |
@stapelberg Hi! Can I already use this package to sync local directory on windows with linux server? |
Depends on what kind of synchronization we’re talking about. If you want to download files from a Linux server, yes. If you want to do bi-directional synchronization: no. As I wrote in the previous message, the daemon does not accept uploads yet. |
Currently, we only implement a sender (for serving files), but a receiver would be neat, too (for downloading files).
Left to do:
The text was updated successfully, but these errors were encountered: