it is possible to make the resize an image that is stored on aws. I have this code that run from another application

var im = require('imagemagick');
var Upload = require('s3-uploader

--config
var client = new Upload('bucket', {

aws: {
region: 'us-west-1',
path: 'imgnormal/',
acl: 'public-read',
accessKeyId: 'KeyID',
secretAccessKey: 'AK',
endpoint: 'https://s3-us-west-1.amazonaws.com',
},cleanup: {
versions: false,
original: false
},
original: {
awsImageAcl: 'public'
},
resize: {
quality: 100
},
versions: [{
maxWidth: 780,
aspect: '3:2!h',
suffix: '-medium'
},{
maxWidth: 320,
aspect: '16:9!h',
suffix: '-small'
}]

});

app.post('/resizeImg',function(req,res){

client.upload('https://s3-us-west-1.amazonaws.com/bucket/imgnormal/house.jpeg', {}, function(err, versions, meta) {

if (err) {
  console.log('----Nope---------', err.message);
  return res.status(400).send('NO');
}
console.log('----Success----', versions, data);
return res.status(200).send('YES');

});

});

when I executo the petition I have the following error

convert.im6: unable to open image `https:/s3-us-west-1.amazonaws.com/bucket/imgnormal/house.jpeg': No such file or directory @ error/blob.c/OpenBlob/2638

what am I doing wrong?

Can you help. How set AWS credentials?

I set in object opts, but create just image with type .jpg.

My code:

versions: [{
    maxHeight: 270,
    maxWidth: 310,
    suffix: '-small',
    quality: 100,
    format: 'png'
  }]

result:

{ quality: 100,
    format: 'jpeg',
    src: '/tmp/gm-e7cf903cd727e32e1097dfd5ca9a55eee94fc8cf-small.jpeg',
    width: 310,
    height: 270,
    etag: 'adcc36a20b17c0053ba7ef987b6c37c5',
    path: 'track_cover/hb/yF/tY-small.jpeg',
    url: 'https://s3.amazonaws.com/welearnfs/track_cover/hb/yF/tY-small.jpeg' }

Apologies if this is mentioned somewhere, I have looked and cannot see it.
When "image.jpg" is uploaded is the name retained in the object but with the suffix appended? The example show is being returned as a long string but I cannot see where this has come from.

Add the possibility to pass AWS credentials directly to the Upload class constructor.

client = new Upload('my-bucket', {
  awsAccessKeyId: String,
  awsAccessSecretKey: String
});

I think we should discontinue support for Node.js v0.10, as mentioned below this version of Node.js is officially discontinued after October 1st 2016.

From nodejs/lts repo:

1. nodejs/node v4.2.0 becomes the current LTS Release
2. joyent/node v0.10 continues in Maintenance only mode until October 1st, 2016
3. joyent/node v0.12 continues as LTS until April 1st, 2016, after which it moves into Maintenance only mode until April 1st, 2017.
4. On or around October 1st, 2016, the second LTS Release from the converged is cut.
5. LTS for v4.2.0 continues until April 1st, 2017, after which it moves to Maintenance mode until around April 1st, 2017.
6. On or around October 1st, 2017, the third LTS Release from the converged is cut.

Just want to pitch this idea here.
I'd like to optimize the resized images before they are uploaded.
What do you think about adding the possibility to let the user do stuff (could be anything) after the images are resized?

OS: Windows 7, 32-bit
Node: 0.12.0
Imagemagick: 6.9.0

client.upload('/uploads/site-logo.png', {}, function(err, versions, meta) {
                  if (err) { throw err; }

                  versions.forEach(function(image) {
                    console.log(image.width, image.height, image.url);
                  });
                });

Please help me on this.

Let's automate the boring part. 😄
Agree/disagree?

http://greenkeeper.io

It knows when your dependencies got updated and simply sends you a pull request with the new package.json.

Should a new version inside your existing version range cause your build to fail, we’ll let you know immediately.

If you’ve got continuous integration tests, they’ll run, and you can keep your software up to date with a single click on GitHub’s merge button.

Pngs resizes to a black transparency as jpeg is the only format it resizes to, It would be nice to be able to detect the png and output pngs rather than jpeg to preserve the image type and properties (such as transparency)

Is it possible to have the 'path' config option to be overridden when an upload takes place?
ie:
client.upload(file, {path: 'imagesJanuary/'}, function(err, images, meta) {...
client.upload(file, {path: 'imagesFebruary/'}, function(err, images, meta) {...

thanks
Jason

I would have liked to be able to clean the original image even if it wasn't uploaded. Currently, the removeVersions function only cleans images that were uploaded.

Also, I would have liked to configure if the original should be uploaded or not without overriding any configuration. For the moment, you need to override an option, such as the awsImageAcl, awsImageExpires, awsImageMaxAge.

Node.js v0.10.32
mageMagick v6.9.0-10
Ubuntu v14.04.1 LTS

the code for the uploader:
var uuid = require('node-uuid');
var config = require('../config');
var _ = require('underscore');
var Upload = require('s3-uploader');

module.exports = {

connect: function() {
    var awsConfig = config.get('s3config');
    console.log(awsConfig);

    try {
        return new Upload(awsConfig.bucket, {
            url: awsConfig.url,
            aws: {
                region: awsConfig.region,
                acl: 'public-read',
                accessKeyId: awsConfig.accessKey,
                secretAccessKey: awsConfig.secretAccessKey,
                endpoint: awsConfig.url,
                s3BucketEndpoint: true
            },
            versions: [{
                original: false
            }, {
                suffix: '-large',
                quality: 80,
                maxHeight: 1040,
                maxWidth: 1040,
            }, {
                suffix: '-medium',
                maxHeight: 780,
                maxWidth: 780
            }, {
                suffix: '-small',
                maxHeight: 320,
                maxWidth: 320
            }]
        });
    } catch (e) {
        console.log('error from uploader connect', e);
    }
},
upload: function(file, client) {
    try {
        client.upload(file, {}, function(err, images, meta) {
            if (err) {
                console.error('Upload Error', err);
            } else {
                for (var i = 0; i < images.length; i++) {
                    console.log('Thumbnail with width %i, height %i, at %s', images[i].width, images[i].height, images[i].url);
                }
            }
        });
    } catch (e) {
        console.log('error from upload', e);
    }
}

}

In the middleware, we call execute the following:
uploader.upload(req.files.uploadedFiles.path, req.uploader);
req.uploader gets set when the application starts and it creates the connection and returns the client.

the error we see is:
{ [Error: Command failed: convert: invalid argument for option `-resize': -auto-orient @ error/convert.c/ConvertImageCommand/2555.
] code: 1, signal: null }

any thoughts?

Ditch CoffeeScript in favour of vanilla JavaScript.

Hi,
I have the following error:

 { [Error: Command failed: Parametro non valido - server\uploads\86caf0d05da8d7fa
 c0fc964368a44939.jpg.mpc
 ] code: 4, signal: null }

In folder server\uploads\ there is the file: 86caf0d05da8d7fac0fc964368a44939.jpg

In myBucket no file is uploaded.

my configuration is:

var client = new Upload('myBucket', {
aws:{
  region: 'eu-west-1',
  acl: 'public-read',
  accessKeyId:'XXXXXXXXXXXXXX',
  secretAccessKey:'XXXXXXXXXXXXXXXXXXX'
},
versions: [{
  original: true
},{
  suffix: '-large',
  quality: 80,
  maxHeight: 1040,
  maxWidth: 1040,
},{
  suffix: '-medium',
  maxHeight: 780,
  maxWidth: 780
 },{
  suffix: '-small',
  maxHeight: 320,
  maxWidth: 320
 }]
});

var filePath='server\uploads\346edfc4433be42e5b85e9927f41b0cf.jpg';

client.upload(filePath, {}, function(err, images, meta) {
  if (err) {
    console.error(err);
  } else {
    for (var i = 0; i < images.length; i++) {
      console.log('Thumbnail with width %i, height %i, at %s', images[i].width, images[i].height, images[i].url);
    }
  }
});

How to set name when i use function upload?

PR #41, and v1.1.0, introduced the possibility to use a custom random path generator such as node-uuid. The benefit with Universally unique identifiers are that they are guaranteed to be unique and we no longer need the collision check which will speed things up a little 😄

This is a breaking change, so this will have to wait for v2.0.0 before we can do the switch.

Which set is correct from below?

awsBucketRegion: 'us-east-1',
awsBucketPath: 'images/',
awsBucketAcl: 'public-read',

OR

aws: {
path: 'images/',
region: 'us-east-1',
acl: 'public-read'
}

Which link from below do we need to follow?
https://github.com/Turistforeningen/node-s3-uploader/blob/stable/0.x/README.md

OR

https://www.npmjs.com/package/s3-uploader

Add new option to delete source image after it has been uploaded successfully.

It is not instantly apparent to me. Thanks.

See: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

us-east-1 is only accessible from s3.amazonaws.com not s3-us-east-1.amazonaws.com

Make all AWS S3 upload options accessible from the #upload() method options – overwriting any globally specified options.

Some more examples on how to use the s3-uploader would be nice. Maybe in an example folder, that way we can more easily integrate them with the test suite making sure no example gets broken between releases.

Provide option to clean up temp files after upload has finished. This should not be necessary when using system default temp directory as this should be clean up automatically. But for custom temp directories this must be done manually.

client.upload('https://s3.amazonaws.com/yadva/uploads/images/mailer_footer.jpg', {}, function(err, versions, meta) {
if (err) { throw err; }

versions.forEach(function(image) {
console.log(image.width, image.height, image.url);
// 1234 4567 https://my-bucket.s3.amazonaws.com/path/ab/cd/ef.jpg
});
res.redirect('back');
});

I'm not able to upload images. Its always throwing error. Please help me on this.

Currently we just return the maxHeight and maxWidth version properties without checking the actual resized image (because this takes time). If someone needs it, they can submit a PR and make it optional for those who needs it.

Provide a constructor option to define a custom random path generator function.

Example:

var uuid = require('uuid');
var Upload = require('s3-uploader');

var client = new Upload('myBucket', {
  randomPathGenerator: uuid.v4
}

Force aspect ratio orientation for resized image; landscape or horisontal.

{
  versions: [{
    maxHeight: 500
    maxWidth: 500
    aspect: '4:3!'
  ]}
}

how to Configuire cloudFront for AWS-SDK?

I have followed this below link:
https://github.com/Turistforeningen/node-s3-uploader/blob/stable/0.x/README.md

OS: Windows 7, 32-bit
Node: 0.12.0
Imagemagick: 6.9.0
[email protected]

My issue is the uploaded image is not having the public read though I have given awsBucketAcl: 'public-read',.

I have use this lib in my project and it works fine in staging. But Image resizing is a cpu intense task, and I can see my staging server cpu usage almost 100% when uploading and resizing a image. Although the staging server is just EC2 t2.micro, I am still afraid that this will lead to server being blocked once pushed to production. (I have tried to upload using two device at the same time and seems to be fine, but still not sure what will happen in production, and the http response takes almost 3000ms!)

Could you tell me how it is handled when multiple users uploading images at the same time and if there is a possibility that the event loop would be blocked which is a big concern in node.js.

My question is also here:

http://stackoverflow.com/questions/34018487/node-js-with-imagemagick-why-server-is-not-blocked

The option to cleanup both original and resized images does not work. In fact there's no reference to it in the code. Am I missing something ?

npm WARN package.json [email protected] cluster is also the name of a node core module.
npm ERR! 404 Not Found
npm ERR! 404
npm ERR! 404 'starefossen/rand-path' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404 It was specified as a dependency of 's3-uploader'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Linux 3.13.0-48-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "s3-uploader"
npm ERR! cwd /home/ubuntu/web-service-api-v2
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code E404
npm ERR! not ok code 0

node version 0.10.33
npm version 1.4.28

Like the title said, do we have option like that.

Make all AWS S3 upload options accessible from Upload class options.

Some files does not have an extension (latest version of expressjs/multer for instance) which crates a problem for s3-uploader. We should add the ability to pass inn one of the following:

a) the original file name
b) file extension
b) image mime type

client.upload('/some/file', { mime: "image/jpeg" }, function(err, versions, meta) {
  ...
});

In some case we need result from on version is enough, so we don't need to wait the entire upload process completed.

For example: I save the original image in database, and sub version deduce from original URL, so the original URL is what I need.

I'm trying to upload some photos as I receive them from a POST request, here is my code:

var multer  = require('multer');
var Upload = require('s3-uploader');
var upload = multer({ dest: 'uploads/' });
var photoRouter = require('express').Router();

// Same as Example in README
var client = new Upload('my-bucket-name', {
  aws: {
    path: 'images/',
    region: 'eu-west-1',
    accessKeyId: 'my-key-id',
    secretAccessKey: 'my-secret-acess-key',
    acl: 'public-read'
  },
  cleanup: {
    versions: true,
    original: false
  },
  original: {
    awsImageAcl: 'private'
  },
  versions: [{
    maxHeight: 1040,
    maxWidth: 1040,
    format: 'jpg',
    suffix: '-large',
    quality: 80,
    awsImageExpires: 31536000,
    awsImageMaxAge: 31536000
  },{
    maxWidth: 780,
    aspect: '3:2!h',
    suffix: '-medium'
  },{
    maxWidth: 320,
    aspect: '16:9!h',
    suffix: '-small'
  },{
    maxHeight: 100,
    aspect: '1:1',
    format: 'png',
    suffix: '-thumb1'
  },{
    maxHeight: 250,
    maxWidth: 250,
    aspect: '1:1',
    suffix: '-thumb2'
  }]
});

photoRouter.post('/', upload.array('photos', 12), postPhoto);

function postPhoto(req, res, next) {

  console.log(req.files);
  // I'm ignoring the posted files, that are correctly saved, and trying to upload the photo I have in the folder
  return client.upload('uploads/profile-picture.jpg', {}, function(err, versions, data) {
    if (err) {
      console.log('Nope', err.message);
      return res.status(400).send('KO');
    }

    console.log('Success', versions, data);
    return res.status(200).send('OK');
  });
}

And here is the error I'm getting:

Nope Command failed: /bin/sh -c identify -format "name=
size=%[size]
format=%m
colorspace=%[colorspace]
height=%[height]
width=%[width]
orientation=%[orientation]
" uploads/profile-picture.jpg
/bin/sh: identify: command not found

I'm using node 4.2.4 on OSX 10.11.2 with s3-uploader 1.1.0

awsBucketAcl: 'public-read'

Which is not making my attachment public. What is the reason for this?
version: [email protected]

Please reply me on this.

hello community have the following doubt'm trying to do the resize an image that I have in the following path of aws /imgnormal/quiko.jpeg

almost copy the code replacing keys aws

 var express = require('express');
 var bodyParser = require('body-parser');
 var im = require('imagemagick'); 
 var Upload = require('s3-uploader');

 var client = new Upload('my-buckets',{

  aws : {
    region : 'us-west-2',
    path : 'images/',
    acl: 'public-read',
    accessKeyId : 'aaaa',
    secretAccessKey  : 'bbbb'
  },
  cleanup: {
    versions: true,
    original: false
  },original: {
    awsImageAcl: 'private'
  },
  versions: [{
    maxHeight: 1040,
    maxWidth: 1040,
    format: 'jpg',
    suffix: '-large',
    quality: 80,
    awsImageExpires: 31536000,
    awsImageMaxAge: 31536000
  },{
    maxWidth: 780,
    aspect: '3:2!h',
    suffix: '-medium'
  },{
    maxWidth: 320,
    aspect: '16:9!h',
    suffix: '-small'
  },{
    maxHeight: 100,
    aspect: '1:1',
    format: 'png',
    suffix: '-thumb1'
  },{
    maxHeight: 250,
    maxWidth: 250,
    aspect: '1:1',
    suffix: '-thumb2'
  }]

});

create this route for test

app.post('/Test', function(req, res) {

  client.upload('imgnormal/quiko.jpeg', {}, function(err, versions, meta) {
      if (err) {
        console.log('----Nope-------', err.message);
        return res.status(400).send('KO');
      }
      console.log('----Success----', versions, data);
      return res.status(200).send('OK');
  });

};

to make the request to the resize the image I have this error

 ----Nope------- Command failed: /bin/sh -c identify -format "name=
size=%[size]
format=%m
colorspace=%[colorspace]
height=%[height]
width=%[width]
orientation=%[orientation]
identify.im6: unable to open image `imgnormal/quiko.jpeg': No such file or directory @ error/blob.c/OpenBlob/2638.

was researching the problem and here's the solution did not have installed imagemagick #73
put the var im = require ( 'imagemagick'); and yet I have this error
in my package.json i have this dependencies

"dependencies": {
    "ejs": "2.3.3",
    "express": "~4.2.x",
    "imagemagick": "^0.1.3",
    "s3-uploader": "^1.1.0"
  },

path the imagemagick https://github.com/rsms/node-imagemagick
what i do wrong in the code?

thanks for your time.

If original image is uploaded to S3 has always been controlled by the version object array.

Etag from AWS contains an extra set of " – "\"9793a0317e715386fbc9fbb8c33894b0\""

I need to set the after bucket, for example:

bucket/mypath/ap-small.jpg

I seem to be getting this error
{ [Error: Command failed: ] code: 1, signal: null }
running my dev environment on Mac OS X 10.10.3
Node.js v0.12.2

my code:

exports.uploadProductImg = function(path, sku){

    var client = new Upload('cdn-hickies', {
        "aws": {region : 'us-east-1',
            path: "/products/" + sku + "/",
            acl: 'public-read'},

        versions: [{
            original: true
        },{
            suffix: '-large',
            quality: 80,
            maxHeight: 1280,
            maxWidth: 1280
        },{
            suffix: '-medium',
            maxHeight: 640,
            maxWidth: 640
        },{
            suffix: '-small',
            maxHeight: 320,
            maxWidth: 320
        },{
            suffix: '-xsmall',
            maxHeight: 150,
            maxWidth: 150
        }
        ]
    });
    client.upload(path, {}, function(err, images, meta) {
        if (err) {
            console.error(err);
        } else {
            for (var i = 0; i < images.length; i++) {
                console.log('Thumbnail with width %i, height %i, at %s', images[i].width, images[i].height, images[i].url);
            }
            require('./inventory-manager').addImages(sku, images);
        }
    });

};