digitalboss/n8n-custom-nodes repository overview

⁠Custom extensions

This image is based on the n8n alpine image with the correspondent version tag.

The first of the directory specified in N8N_CUSTOM_EXTENSIONS gets created and will be the install directory for custom modules (Delimiter ;) example -e N8N_CUSTOM_EXTENSIONS="/home/jim/n8n/custom-nodes;/data/n8n/nodes"

Custom modules are installed according to $CUSTOM_MODULES (Delimiter ;) example -e CUSTOM_MODULES="@digital-boss/n8n-nodes-woocommerce;@digital-boss/n8n-nodes-odoo"

Custom modules with unsafe-perms are installed according to $CUSTOM_MODULES_UNSAFEPERM (Delimiter ;) example -e CUSTOM_MODULES_UNSAFEPERM="@digital-boss/n8n-nodes-dnc-suitecrm"

Custom modules for functions according to NODE_FUNCTION_ALLOW_EXTERNAL (such as date-fns) will be installed to /usr/local/lib “alongside of n8n” (Delimiter ,) example -e NODE_FUNCTION_ALLOW_EXTERNAL="date-fns,date-fns-tz,feiertagejs"

Custom apk (package manager for alpine) are installed according to $CUSTOM_APK (such as openssh) the alpine image (Delimiter ;). example -e CUSTOM_APK="openssh;"

⁠Use with n8nio/n8n images

(Works only with custom modules!) If you want to use the standard n8n image, you can only use this image for node installation purposes: Spin up a container with a mounted volume and then mount the same volume to a container using the standard image. example -v n8n_data:/home/node/.n8n

⁠Update

The installation will run only on the first start of the container. Thus, you need to recreate the container in order to update the custom modules.