blitline-dev/blitline_node

Simple NodeJS wrapper for Blitline.com service

blitline_node's Issues

Pre-process move-original for Azure

Hi,

There appears to be a way to move the original to an Amazon S3 container via the beta pre-process feature.

From the example:

{
    "application_id":"YOUR_APP_ID",
    "src":"http://cdn.blitline.com/filters/boys.jpeg",
    "pre_process":{
        "move_original":{
            "s3_destination":{
                "bucket":"bltemp",
                "key":"grumpy_squirrel/moved_original_foo23.png"
            }
        }
    },
    "functions":[
        {
            "name":"resize_to_fit",
            "params":{
                "width":100
            },
            "save":{
                "image_identifier":"MY_CLIENT_ID"
            }
        }
    ]
}

Is there a way to specify a Microsoft Azure blob container instead?

Ability to set custom AWS headers in addSave?

Hey there,

We need to ensure that all images saved by Blitline have public read disabled, and are accessible only via expiring REST API URLs.

As discussed on the S3 Headers page, Blitline should be able to handle this. But it looks like custom headers are not yet supported by this module, is that correct?

I did a bit of digging and I can see the Save and S3_Destination classes, but I'm not clear how exactly to go about modifying the current save behavior to take an optional set of S3_headers should they exist.

Is there a way to use a plain addFunction call to save with additional vars? Is this feature something which might be released shortly?

Thanks,
Ethan

Blitline Response gets cut off

I was getting "unexpected end of input" errors sending multiple jobs in one blitline request. Took a look at the source and it looks like the lib returns too early. I believe it should wait for an end signal

New to node, and short on time, but this worked for me if someone wants to do an update to this repo.

in blitline.js: postJobs()

var resp_body = "";
request.on('response', function (response) {
response.setEncoding('utf8');
response.on('data', function (chunk) {
resp_body += chunk;
});

response.on('end', function () { callback(resp_body);});

Error: "undefined method `user_id' for nil:NilClass"

Hi, guys,

Code that was working fine has suddenly started throwing the following:

{"results":"undefined method `user_id' for nil:NilClass"}

This looks like a Ruby error and we don't have any ruby on our end.

The calling code is a bit like this:

        const job = {
            json: {
                src: "sourceUrl",
                functions: [{ name: 'xx', params: xx, save: xx}]
            }
        };

          blitline.process(job); // This returns an error

Status of this package?

Is this package fully built out? Several of the features do not seem to connect? Or maybe we are missing something in the implementation. Can you provide an example of how to include s3_destination parameters for addFunction / addSave?

We see the the S3Destination in the lib.

NPM Error: No compatible version found: blitline

I'm getting this error when I use npm to install blitline:

   npm ERR! Error: No compatible version found: blitline
   npm ERR! No valid targets found.
   npm ERR! Perhaps not compatible with your version of node?
   npm ERR!     at installTargetsError (/tmp/node-npm-UStX/lib/cache.js:424:10)
   npm ERR!     at /tmp/node-npm-UStX/lib/cache.js:406:17
   npm ERR!     at saved (/tmp/node-npm-UStX/lib/utils/npm-registry-client/get.js:136:7)
   npm ERR!     at cb (/tmp/node-npm-UStX/node_modules/graceful-fs/graceful-fs.js:36:9)
   npm ERR! Report this *entire* log at:
   npm ERR!     <http://github.com/isaacs/npm/issues>
   npm ERR! or email it to:
   npm ERR!     <[email protected]>
   npm ERR!
   npm ERR! System Linux 2.6.32-343-ec2
   npm ERR! command "/tmp/node-node-hmaq/bin/node" "/tmp/node-npm-UStX/cli.js" "install" "--production"
   npm ERR! cwd /tmp/build_21ikurogvfndo
   npm ERR! node -v v0.4.7
   npm ERR! npm -v 1.0.106
   npm ERR!
   npm ERR! Additional logging details can be found in:
   npm ERR!     /tmp/build_21ikurogvfndo/npm-debug.log
   npm not ok