Nexrender: Customizing nexrender-node

[iadj]

I want to try to make some changes/improvements to nexrender-node, but I'm not too familiar with globally installed CLI node applications. After installing nexrender to a directory and making some changes (to i.e. tasks), how do I get nexrender-node to use my changes? I don't necessarily need to globally install my changed version.

[iadj]

Figured it out: node cli.js --renderer

[inlife]

yep :D
btw, what changes did you make, im very curious ? 😊

[iadj]

@Inlife Trying to make a JPEG Sequence project render in parallel with multiple nodes, and zipping each successful render. The ZIPs should then be uploaded to a 'master' node to compress into a video format!
Currently working in actions.js to try and zip the resulted JPEGs and then sending a ZIP containing the frames to results folder.

[iadj]

@Inlife Maybe using API project.on('finished'... is a better way to achieve this?

[inlife]

i think you war is the good way
i thought about this way of achieving multi-sequence rendering

ill be glad to see that as a pull request, if you want to ! :D

[iadj]

@Inlife If I can get it to work :D

[inlife]

the idea is that you are creating few projects at runtime, and one of them is "master"
he will have it's status set to "waiting" for example (this way it wont be pulled by render-node)
as soon as all projects will finish rendering (you can have a Promise.all callback using api)
you can change status to "queued" and it will be handled by one of the rendernodes

sharing of images can be achieved by using more simple ways, for example: native os shared folder
or shared folder via some of the programs such as bittorrent-sync, or dropbox, or smth like that

thats only my thoughts tho :)

[southernsun]

for sharing images: just use npm connect and serve-static to quickly setup a http server to host your files.. that's what i'm doing for my test environment.

var connect = require('connect');

var serveStatic = require('serve-static');
connect().use(serveStatic(__dirname)).listen(8080, function(){
console.log('Server running on 8080...');
});

[inlife]

@southernsun there is also that (imo more convinient) tool:
https://www.npmjs.com/package/http-server
you can start server like this:
$ http-server -p 8080