@mojodna/tp v0.1.0

'tp

Putting the tee in HTTP.

This acts as a reverse proxy and tees responses into S3 for semi-permanent storage. It's intended to be used with Varnish as a secondary backend (to serve up and populate S3 misses).

Purging the S3 Bucket

This will empty the configured S3 bucket of everything:

foreman run node bin/purge.js

It's intended to be used when cached content is being refreshed, before Varnish is purged.

Configuration

tp.json:

{
  "/background/": {
    "origin": "http://background.example.com"
  },
  "/features/": {
    "origin": "http://features.example.com"
  },
  "/labels/": {
    "origin": "http://labels.example.com"
  },
  "/": {
    "origin": "http://default.example.com",
    "pathPrefix": "default"
  }
}

Environment Variables

• S3_BUCKET - Target S3 bucket
• S3_URL - S3 URL, defaults to http://s3.amazonaws.com
• AWS_ACCESS_KEY_ID - AWS Access Key ID
• AWS_SECRET_ACCESS_KEY - AWS Secret Access Key
• CACHE_EVERYTHING - treat everything as cacheable (optional), regardless of upstream Cache-Control headers
• NODE_ENV - Express environment (should be production in production)