aliyun oss storage adapter for keystonejs
Last updated 5 months ago by xiaoqiang.yang .
MIT · Repository · Bugs · Original npm · Tarball
$ cnpm install keystone-storage-adapter-ali-oss 
SYNC missed versions from official npm registry.

ali-oss-based storage adapter for KeystoneJS


Configure the storage adapter:

var storage = new keystone.Storage({
  adapter: require("keystone-storage-adapter-ali-oss"),
  oss: {
    endpoint: "", // required; defaults to process.env.OSS_ENDPOINT
    accessKeyId: "key", // required; defaults to process.env.OSS_KEY
    accessKeySecret: "secret", // required; defaults to process.env.OSS_SECRET
    bucket: "mybucket", // required; defaults to process.env.OSS_BUCKET
    path: "/upload",
    headers: {
      "x-public-read": "public-read" // add default headers; see below for details
  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:

  name: { type: String },
  file: { type: Types.File, storage: storage }


  • endpoint: (required) Ali-oss endpoint to connect to.

  • accessKeyId: (required) Ali-oss access key. Configure your Aliyun credentials in the IAM console.

  • accessKeySecret: (required) Ali-oss access secret.

  • bucket: (required) ali-oss bucket to upload files to. Bucket must be created before it can be used.

  • 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 ali-oss. You can use these headers to configure lots of additional properties and store (small) extra data about the files in ali-oss itself.


The 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.


Licensed under the standard MIT license. See LICENSE.

Maintainers (1)
Today 0
This Week 0
This Month 7
Last Day 0
Last Week 7
Last Month 6
Dependencies (4)
Dev Dependencies (3)
Dependents (0)

Copyright 2014 - 2016 © |