Static Site

Minimal Alpine Linux Docker image with nginx, awscli and gomplate. Also included are scripts for deploying to S3 and templating files.

This is useful as an intermediate container for holding static website build artefacts. This image can then be used as a container for holding a static website. And the resulting image artefact can be used to serve the site, or used to deploy the site to an S3 website bucket, or a bucket backed CloudFront distribution.

Entrypoint Commands

• nginx - Serve static files from /var/www/html (default)
• s3sync - Synchronize the files in /var/www/html with a S3 bucket (uses awscli).
• templater - Write out gomplate templates. Useful for generating env.js configuration for dynamically configurable JS apps.

For templater the usage is as follows: templater <source_template> <output_file>

All templates must be written to utilise environment variables.

Configuration / Environment Options

For s3sync:

• AWS_ACCESS_KEY - AWS Access Key (optional)
• AWS_SECRET_KEY - AWS Secret Key (optional)
• AWS_BUCKET_NAME - AWS Bucket Name (required).
• CACHE_CONTROL_DEFAULT="public, max-age=3600" - Default Cache-Control header to set (optional).
• CACHE_CONTROL_DEFAULT_OVERRIDE="public, max-age=60, s-maxage=60" - Alternate default Cache-Control header (optional).
• CACHE_CONTROL_OVERRIDE_N - Override the Cache-Control header for a file.

Cache Control Override

CACHE_CONTROL_OVERRIDE_N can be defined as FILE:VALUE eg. index.html:public max-age=30. If VALUE is exclude the CACHE_CONTROL_DEFAULT_OVERRIDE is used. Multiple overrides can be set by changing _N. Can be replaced with any alphanumeric value eg CACHE_CONTROL_OVERRIDE_INDEX and CACHE_CONTROL_OVERRIDE_404.

Status

Experimental.

Known issues

• When using s3sync the cache-control will only be updated when the file is also updated.

TODO

• Implement similar Cache-Control functionality for Nginx hosted static sites.