hmp-upyun-sdk
v1.0.0
Published
[![NPM version](https://img.shields.io/npm/v/upyun.svg?style=flat-square)](https://www.npmjs.org/package/upyun) [![NPM downloads](https://img.shields.io/npm/dm/upyun.svg?style=flat-square)](https://www.npmjs.org/package/upyun) [![Build status](https://img
Downloads
5
Readme
node-upyun
official upyun sdk for node.js
Currently only works with legacy
API(the current online API)
Install
$ npm install upyun --save
Init
var upyun = new UPYUN(bucket, operator, md5(password), endpoint, apiVersion);
Arguments
bucket
: your upyun bucket's name.operator
: operator which is granted permisson tobucket
md5(password)
: md5 signed passowrd for the operator which is granted permisson tobucket
endpoint
The value can be these(leave blank to let sdk auto select the best one):ctcc
orv1
: China Telecomcucc
orv2
: China Unicomcmcc
orv3
China Mobilev0
or any other string: Will usev0.api.upyun.com
(auto detect routing)
apiVersion
: API version.'legacy'
: current online api.(currently, it is the default)- when you choose
legacy
, it make an instance by upyun-legacy, they have the same methods name as thelatest
version. But the response data may not has the same format. More detail at upyun-legacy/README.md
- when you choose
'latest'
: the bleeding-edge.(Not available now.)
Example
var UPYUN = require('upyun');
var upyun = new UPYUN('testbucket', 'operatername', 'md5(operaterpwd)', 'ctcc', 'legacy');
upyun.getUsage(function(err, result) {
//...
})
Response
In this SDK, every api will return a response in the format:
Normal
{
statusCode: 200, // http stats code
headers: {
server: 'nginx/1.1.19',
date: 'Wed, 13 Aug 2014 02:15:27 GMT',
'content-type': 'application/json',
'content-length': '24',
connection: 'close'
}, // response header
data: {
space: 2501,
files: 1
} // response body
}
Error catch
When an error occured, the error will be catched, and returned in the response
{
statusCode: 401, // http stats code
error: {
error_code: 40104,
request: 'GET /imgtest',
message: 'Signature error, (signature = md5(METHOD&PATH&DATE&CONTENT_LENGTH&MD5(PASSWORD))).'
}, // error message
headers: {
server: 'nginx/1.1.19',
date: 'Wed, 13 Aug 2014 02:19:07 GMT',
'content-type': 'application/json',
'content-length': '145',
connection: 'close',
'www-authenticate': 'Basic realm="UpYun"'
} // response header
}
The different between these two responses is the error
and body
.
All responses contain http status code and raw response header for futher usage.
Docs
API
Utils
API
Response
{
statusCode: 200,
headers: { ... },
data: {
space: 21754,
files: 50
}
}
Arguments
remote_dir_path
The dir path which you want to traverse.limit
Specifies the maximum number of file list output per request.order
Sort the file list by 'last_modified' asasc
ordesc
.(Default:asc
)iter
Specifies the start of iteration.
Response
{
statusCode: 200,
headers: {...
},
data: {
"files": [{
"name": "test",
"type": "folder",
"last_modified": 1412046146
}],
"iter": "g2gCZAAEbmV4dGQAA2VvZg"
}
}
Arguments
remotePath
The dir path which you want to create.
remotePath
The dir path which you want to remove.
Arguments
remotePath
Where the file will be stored in your UPYUN bucket.localFile
The file you want to upload. It can be apath
string or the file's raw data.type
Specifies the file's content-type.checksum
Settrue
to force SDK send a md5 of local file to UPYUN. Or set a md5value string by yourself.opts
The additional http request headers(JavaScript Object). More detail in Official Docs
Arguments
remotePath
The file's path in your UPYUN bucket.
Arguments
remotePath
The file's path in your UPYUN bucket.localPath
Where the file will save to. If nolocalPath
, the file's content will output directly in the response body.
Arguments
remotePath
The file's path in your UPYUN bucket.
Utils
Arguments
endpoint
The value can be these(leave blank to let sdk auto select the best one):ctcc
orv1
: China Telecomcucc
orv2
: China Unicomcmcc
orv3
China Mobilev0
or any other string: Will usev0.api.upyun.com
(auto detect routing)
Note
The previous owner of upyun npm package
was James Chen
After consultation with James, this package has been transfered to official upyun develop team.
Any futher update and maintenance will conducted by upyun develop team and subsequent versions will not be associated with the original project.
In npm registry, "upyun": "<=0.0.3"
were published as node-upyun by James Chen.
Thanks to James Chen for his contribution to UPYUN.