How to update only newer file?

[higimo]

I have upload 1 gb every deploy. But update 2 files. How upload onli this newer files?

[simonh1000]

Sorry, but that's not supported at present. I'd find it useful too, but have no timeline to develop it.

A number of people have had a go at this now

1. @TomFreudenberg (Incremental Update based on a folder-hash file #117) based on a storing a file of MD5s each time ftp-deploy is invoked
2. @limikael (added newFilesOnly #151) uses a more reliable date comparison
3. @paganaye (implement updateNewerFiles option #141) who proposes storing a file on the destination (essentially of name and date)
4. me ([wip] Upload newer #100) based on file size and date comparison

I'm not excited about creating extra files (state) and storing them on people's computers, but adding the MD5 is perhaps the gold standard in comparing. However, MD5ing a 1 GB file (such as motivated some of the contributors of PRs) is expensive in other ways

I think my preference is for solution 2, and does work well in the PHP use case. It may not be perfect but perhaps good enough, not least as so many developers now enjoy git-style deploys anyway

Would welcome thoughts

[simonh1000]

@higimo if you have time to test this branch https://github.com/simonh1000/ftp-deploy/tree/upload-newer, that would be much appreciated

[gabrielnvg]

@higimo if you have time to test this branch https://github.com/simonh1000/ftp-deploy/tree/upload-newer, that would be much appreciated

I tested, and in my case, I generate a build folder every time before deploying.
Therefore, my files will always have a newer date.

Maybe it's a good idea to pass as parameters the options to choose between only update if file is newer, only if size is different, or only if both (and in my case, I would choose only if size is different).

In time, nice job on this project!
It saved me a lot of time :)

[mhadaily]

I have a proposal on this, what if we create hashtable of files and when you upload you upload like a .state.json and every time we want to upload, we can upload compare hash files, and if any difference, then we upload. that makes sure we upload when there is actually a difference and that could work on any environment,

What do you think?

[simonh1000]

I'm reluctant to do that @mhadaily because it create an extra piece of state that could get out of sync. I know that I have sometimes switched to an ftp client to upload a bugfix to a specific file (perhaps when I was away from my main machine) so that the state.json you propose could end up being inaccurate. The solution in the PR works for e.g. php sites - I think (that's why it needs testing) - but not, as @gabrielnvg notes, for projects that compile the distributed assets.

There do seem to be ways that work, but I have not tried to look at the source code of e.g. the grunt ftp client I used back in the day which seemed to work quite nicely

[TomFreudenberg]

Hi maybe you checkout this approach - is working well on our side #117