Question: How to specify a render temporary directory to be used when rendering?

[avisiedo]

Hi all,

I have been able to run terminalizer in a pipeline, using headless electron (applying this patch: #134), and executing the process by xvfb-run -d -w 60 wrapper-to-render.sh ....

ELECTRON_DISABLE_GPU=1 terminalizer render --output 001-install-client-tools.gif 001-install-client-tools
Successfully Rendered
The animated GIF image is saved into the file:

The situation I am facing is to make possible to launch several terminalizer instances rendering different files at a time; however, I have crashed with a situation where the render action is using a static path in node_modules; when the first task finish, remove the files, evoking to fails the remaining tasks (and I guess this will be overwritten files, so that the animation could mix frames from different renders, which is something to avoid).

ELECTRON_DISABLE_GPU=1 terminalizer render --output 001-install-client-tools.gif 001-install-client-tools
Error: 
  Error: ENOENT: no such file or directory, open '/home/gitlab-runner/.npm-packages/lib/node_modules/terminalizer/render/frames/166.png'
Hint:
  Use the --help option to get help about the usage

I was wondering if there are some workaround to use a path provided externally for the render path, so that I can create a temporary directory by mktemp -d /tmp/terminalizer.render.XXXXXXXX command, and pass that temporary path to terminalizer. Such as:

export TERMINALIZER_RENDER_PATH="$( mktemp -d /tmp/terminalizer.render.XXXXXXXX )"
terminalizer render demo
rm -rf "${TERMINALIZER_RENDER_PATH}"

If such variable exists, I would be more than happy to know about it :) It would allow me to explode all the power for the pipeline runner, launching several jobs for rendering at a time.