inossidabile / grunt-ftpush

Grunt task for incremental code deployment over ftp

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Query about how it decides the state

Melindrea opened this issue · comments

So, now it's working very nicely, but I have one question about how it decides that something needs to be reuploaded.

My usecase is the following: Using grunt I build the deploy version, which is the one one that gets uploaded. Every time I build it, it cleans out the prior versions, and I now noticed that it will re-upload every single file, not just the ones that's actually changed (should've been one file changed, one removed and one added in my particular experiment).

I take it that rather than comparing the hash, it compares modification date? Or is it working off of something else that changes when I build a fresh copy?

Yes, exactly. It's comparing the modification date. But probably using a hash would be wiser. I'm on it.

Use 0.2.0.

Awesome =)

Boris Staal notifications@github.com skrev:

Use 0.2.0.


Reply to this email directly or view it on GitHub:
#6 (comment)

Skickat från min Android-telefon med K-9 E-post. Ursäkta min fåordighet.