Running n8n as global package in prod

Questions
1

Describe the problem/error/question

Hi, i switched off docker running n8n as the npm -g package. Everything works fine execpt that the “white label” shows n8n is running in DEV mode + i dont get the popups of update available like when it was in docker.

is there ENV var to turn it ti “prod” and get the updates available?

my systemd service has

Environment="NODE_ENV=production"
Environment="WEBHOOK_URL=url"
Environment="VUE_APP_URL_BASE_API=url"
Environment="GENERIC_TIMEZONE=Europe/Berlin"
Environment="NODE_FUNCTION_ALLOW_EXTERNAL=*"
Environment="NODE_FUNCTION_ALLOW_BUILTIN=*"

What is the error message (if any)?

image

Thank you

Debug info

core

  • n8nVersion: 1.68.0
  • platform: npm
  • nodeJsVersion: 22.0.0
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 2bb6fb9a-e036-4857-b9fe-26efe698ef68

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @kristus

May I ask why you moved away from Docker? This is the recommended way of hosting n8n.

Updates are always available as long as you update it. It will not automatically update normally.
Not sure how to remove the DEV though,

4

two main reasons.

  1. On that machine i used docker just for n8n. Figured why to waste resources running docker if i can run it directly.
  2. It made it much more easier to use custom cli_tools (via Execute command node) in workflows from that machine. Beofer that it was rather unpleasent

I can see in the Dockerfile they use

npm install -g --omit=dev n8n@${N8N_VERSION} --ignore-scripts

but wasnt sucessful with that.,

I am running it as npm package on my homelab for some time and few months back the logo was still wihout DEV for npm global package, it is quite recently added so it was a conscious decision from someone on the dev team

5

can you please try setting N8N_RELEASE_TYPE=stable in the env variables.

1 Like
6

Hi, yes thats the one. Thank you.
It fixed both the logo + the updateAvailable modal

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.