Skip to content
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

Implemented tracking of changes to s3 assets #93

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

coen-hyde
Copy link
Contributor

Implemented tracking of changes to s3 assets. It's off by default and can be turned on by setting the option flag 'trackChanges'. I use this to invalidate cache. In particular with Fastly with this grunt plugin (https://github.com/coen-hyde/grunt-fastly).

@dmikey
Copy link
Collaborator

dmikey commented Nov 8, 2013

I'll be looking through this PR in the next few days, just notifying people that someone is on these.

@imrane
Copy link

imrane commented Nov 26, 2013

nice - been looking around for an easy way to invalidate my s3 files

@zdexter
Copy link
Collaborator

zdexter commented Dec 11, 2013

Could you rebase this on top of master and resolve any conflicts?

… record-changes

* 'master' of https://github.com/pifantastic/grunt-s3:
  Log bucket and destination on upload
  Headers were broken when upload a lot of large files (and set maxOperations to 5). Could be also relevant with issue pifantastic#100.
  Mention that verify is an option and be more specific as to where it can be set
  Add documentation for the 'rel' option.
  Fixed the options in some of the documentation examples
  Update readme
  Reduce verbosity
  v0.2.0-alpha.3
  update sync messages too
  oops, missed a src
  don't bring tmp gzip path

Conflicts:
	README.md
	tasks/lib/s3.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants