genroc/eval-node repository overview

⁠genroc/eval-node

The script-task worker for genroc⁠. It claims TypeScript and JavaScript script tasks from a genroc server's queue and runs each one in a fresh worker thread.

docker run -e GENROC_SERVER=http://genroc:8448 genroc/eval-node:latest

The worker connects to genroc, not the other way round, so it needs only outbound access and no published ports.

This image only runs scripts. Bundling and typechecking happen on your machine, through the @genroc/eval-node⁠ npm package that genctl apply calls. To scaffold a project with both, run genctl init --eval-node.

⁠Compose

services:
  eval-node:
    image: genroc/eval-node:latest
    environment:
      GENROC_SERVER: http://genroc:8448
    restart: unless-stopped

To run more scripts at once, scale the service or raise CONCURRENCY.

⁠Environment

With auth enabled, create a token that has only the worker permission, and mount it as a file so it stays out of docker inspect:

genctl token create --perms worker --label evaluator -q > worker-token
docker run -e GENROC_SERVER=http://genroc:8448 \
  -e GENROC_TOKEN_FILE=/run/worker-token -v "$PWD/worker-token:/run/worker-token:ro" \
  genroc/eval-node:latest

If the token is rejected, the container exits instead of retrying.

⁠Tags

A release tags the genroc server, this image and the @genroc/eval-node package with the same version.

⁠Notes

• Not a sandbox. Scripts get the container's filesystem, network and environment. Run only code you trust.
• Memory is not isolated. A script that runs out of memory takes down the whole worker. Run it with restart: unless-stopped.
• Also on ghcr.io/genroc/eval-node.

Docs: TypeScript evaluation⁠ · Source: https://github.com/genroc/genroc/tree/main/eval-node⁠