Closed mibamur closed 10 years ago
Interesting idea. Checking the update date wouldn't be reliable, since it's not necessarily always the same machine releasing. The file size could also cause problems if a file has been changed but is size happens to remain the same.
What about storing an internal manifest file containing a md5 of all files, and checking both hashes in order to decide whether we want to upload or not?
I thinking about md5. Can We/ I /You add this options and how do it right?
localrepo
remote
get manifest.remote
if manifest.local != manifest.remote {
compare manifest.local.Hash manifest.remote.Hash
# where Hash { file1, md5 }
}
You mean like that?
Yes, I think you got the idea. Unfortunately, I don't think I'll have the time to implement this in the near future. Feel free to work on it, I'll be glad to review any PR.
ok, I`ll do it
Don't close this issue, as it's not fixed yet ;)
in works
I'm actually going to close this, since it's not a bug but a feature request and it's going stale. Anybody wants to work on it, feel free to open a PR.
I made it but can not find better place where I may paste my code.
Looking forward to it. The suspense!
Any news?
I will do it next week! I promise :)
Hello!
I have some big images and many js duplicate libarary for "when CDN fail", and when I load all files and dirs to host - spend more time.
Solve problem:
ftp_exclude: [ '/js', '/img/*', 'README.md' ]
or read exclude from like.gitignore
but.glyynignore
or.ftpingnore
ftp_replace: all | size | time