README.md in s3_website-2.13.0 vs README.md in s3_website-2.14.0
- old
+ new
@@ -275,10 +275,20 @@
```
Once you've saved the configuration into `s3_website.yml`, you can apply them by
running `s3_website cfg apply`.
+#### Invalidating all CloudFront resources (wildcard invalidation)
+
+The following setting is recommended for most users:
+
+```yaml
+cloudfront_wildcard_invalidation: true
+```
+
+Over time, it can reduce your AWS bill significantly. For more information, see <http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html>.
+
#### Invalidating root resources instead of index.htmls
By default, `s3_website push` calls the CloudFront invalidation API with the
file-name-as-it-is. This means that if your file is *article/index.html*, the
push command will call the invalidation API on the resource
@@ -474,10 +484,15 @@
If you are not sure how to test your pull request, you can ask the [gem owners
](http://rubygems.org/gems/s3_website) to supplement the request with tests.
However, by including proper tests, you increase the chances of your pull
request being incorporated into future releases.
+## Alternatives
+
+* <https://pages.github.com/>
+* <https://pages.gitlab.io/>
+
## License
MIT. See the LICENSE file for more information.
## Contributors
@@ -521,9 +536,13 @@
* Tate Johnson
* Toby Marsden
* Tom Bell
* Trevor Fitzgerald
* Zee Spencer
+
+## Community articles
+
+* [Deploying websites to FTP or Amazon S3 with BitBucket Pipelines](https://www.savjee.be/2016/06/Deploying-website-to-ftp-or-amazon-s3-with-BitBucket-Pipelines/)
## Donations
[](https://www.gittip.com/laurilehmijoki/)