Define your build sources in HTML.
This is a router abstraction for gulp-awspublish, allowing you to define options like caching, key manipulation and such on a per-file basis. The routes are specified similarly to Apache, where the route rules are RegExps processed one by one and when a match is found, the "redirect" is specified using RegExp backreferences.
You can install gulp-awspublish-router via npm:
$ npm install --save-dev gulp-awspublish-router
Include the plugin:
var awspublishRouter = ;
This is a function that takes an options object as its argument, and the options are as follows:
routesA key-value pair of the routes and their options.
cache(optional) Override values for default cache options:
null) a value in seconds to use for cache headers. If
null, no cache headers are applied.
true) a boolean value on whether to include the
publicdirective in the
Cache-Controlheader. If false,
privatedirective is used instead.
false) a boolean value on whether to allow transforms of the cached content. If
no-transformdirective is applied to the
false) if specified, applies the
Expiresheader as well. Use with caution as the cache will expire after the
cacheTimehas passed of the publish time.
var awspublish = ;var awspublishRouter = ;gulp;
Contributions are most welcome! If you're having problems and don't know why, search the issues to see if someone's had the same issue. If not, file a new issue so we can solve it together and leave the solution visible to others facing the same problem as well. If you find bugs, file an issue, preferably with good reproduction steps. If you want to be totally awesome, you can make a PR to go with your issue, containing a new test case that fails currently!
Development is pretty straightforward, it's all JS and the standard node stuff works:
To install dependencies:
$ npm install
To run the tests:
$ npm test
Then just make your awesome feature and a PR for it. Don't forget to file an issue first, or start with an empty PR so others can see what you're doing and discuss it so there's a a minimal amount of wasted effort.
Do note that the test coverage is currently a whopping 100%. Let's keep it that way! Remember: if it's not in the requirements specification (i.e. the tests), it's not needed, and thus unnecessary bloat.