Sha256: 5b1d6391189ada0dcd7398b84dad29e5413fed80094160dd89781babb479a41a
Contents?: true
Size: 1.37 KB
Versions: 10
Compression:
Stored size: 1.37 KB
Contents
# Example `s3_website` configurations This document shows examples of complete `s3_website.yml` configurations. ## Minimal ````yaml s3_id: abcd s3_secret: 2s+x92 s3_bucket: your.domain.net ```` ## Minimal with EC2 AIM roles ````yaml s3_bucket: your.domain.net ```` If you run `s3_website` on an EC2 instance with IAM roles, it is possible to omit the `s3_id` and `s3_secret`. ## Optimised for speed: using CloudFront, gzip and cache headers ````yaml s3_id: <%= ENV['your_domain_net_aws_key'] %> s3_secret: <%= ENV['your_domain_net_aws_secret'] %> s3_bucket: your.domain.net cloudfront_distribution_id: <%= ENV['your_domain_net_cloudfront_distribution_id'] %> cloudfront_distribution_config: default_cache_behavior: min_TTL: <%= 60 * 60 * 24 %> aliases: quantity: 1 items: CNAME: your.domain.net max_age: 120 gzip: true ```` Above, we store the AWS credentials and the id of the CloudFront distribution as environment variables. It's convenient, since you can keep the `s3_website.yml` in a public Git repo, and thus have your deployment configurations version-controlled. ## Using redirects ````yaml s3_id: hello s3_secret: galaxy redirects: index.php: / about.php: about.html routing_rules: - condition: key_prefix_equals: code/repositories/git/ redirect: host_name: git.johnny.com replace_key_prefix_with: "" http_redirect_code: 301 ````
Version data entries
10 entries across 10 versions & 1 rubygems