@coatilabs/keystone-image-manipulation-storage-adapter-s3

S3-based storage adapter for KeystoneJS with Jimp integration.

This adapter is designed to replace the existing S3File field in KeystoneJS using the new storage API, modified to manipulate images after upload with Jimp tool.

Tested in Node.js 6.12.2

Usage

Configure the storage adapter:

var storage = new keystone.Storage({
  adapter: require('keystone-storage-adapter-s3'),
  s3: {
    key: 's3-key', // required; defaults to process.env.S3_KEY
    secret: 'secret', // required; defaults to process.env.S3_SECRET
    bucket: 'mybucket', // required; defaults to process.env.S3_BUCKET
    region: 'ap-southeast-2', // optional; defaults to process.env.S3_REGION, or if that's not specified, us-east-1
    path: '/profilepics',
    headers: {
      'x-amz-acl': 'public-read', // add default headers; see below for details
    },
    manageImage: function(file, callback) {
      // Here you can manipulate file
      callback(null, file);
    }
  },
  schema: {
    bucket: true, // optional; store the bucket the file was uploaded to in your db
    etag: true, // optional; store the etag for the resource
    path: true, // optional; store the path of the file in your db
    url: true, // optional; generate & store a public URL
  },
});

Then use it as the storage provider for a File field:

File.add({
  name: { type: String },
  file: { type: Types.File, storage: storage },
});

Options:

The adapter requires an additional s3 field added to the storage options. It accepts the following values:

• key: (required) AWS access key. Configure your AWS credentials in the IAM console.

• secret: (required) AWS access secret.

• bucket: (required) S3 bucket to upload files to. Bucket must be created before it can be used. Configure your bucket through the AWS console here.

• region: AWS region to connect to. AWS buckets are global, but local regions will let you upload and download files faster. Defaults to 'us-standard'. Eg, 'us-west-2'.

• path: Storage path inside the bucket. By default uploaded files will be stored in the root of the bucket. You can override this by specifying a base path here. Base path must be absolute, for example '/images/profilepics'.

• headers: Default headers to add when uploading files to S3. You can use these headers to configure lots of additional properties and store (small) extra data about the files in S3 itself. See AWS documentation for options. Examples: {"x-amz-acl": "public-read"} to override the bucket ACL and make all uploaded files globally readable.

• manageImage: (function; default: copies same file) Method to manipulate your image file

  • See Jimp for additional documentation.

Schema

The S3 adapter supports all the standard Keystone file schema fields. It also supports storing the following values per-file:

• bucket, path: The bucket, and path within the bucket, for the file can be is stored in the database. If these are present when reading or deleting files, they will be used instead of looking at the adapter configuration. The effect of this is that you can have some (eg, old) files in your collection stored in different bucket / different path inside your bucket.

The main use of this is to allow slow data migrations. If you don't store these values you can arguably migrate your data more easily - just move it all, then reconfigure and restart your server.

• etag: The etag of the stored item. This is equal to the MD5 sum of the file content.

License

Licensed under the standard MIT license. See LICENSE.