setting NODE_ENV for production

[sparkwise]

I noticed while while restarting the Etherpad app that it is currently loading in development mode.

[WARN] settings - Etherpad is running in Development mode. This mode is slower for users and less secure than production mode. You should set the NODE_ENV environment variable to production by using: export NODE_ENV=production

In which file should I add NODE_ENV=production? I'm not seeing anything in the File Manager for environment variables.

[luckow]

I never thought about it. Is there a difference in = production?

[robi]

See if there is a .env file

[sparkwise]

It looks like Cloudron is trying to set NODE_ENV=production in start.sh:57, but this clearly isn't working based on what is in the logs.

@robi Adding a .env file with NODE_ENV=production unfortunately didn't change this.

@luckow Warning message in the logs says "This mode is slower for users and less secure than production mode."

Wanted to flag that I see an example in the Etherpad documentation that sets this via Docker Compose: https://docs.etherpad.org/docker.html#:~:text=NODE_ENV%3A production

[robi]

Hmm the start script uses gosu which runs as a different user which may prevent the env from following

It also runs pnpm dev, which may override?

[nebulon]

Latest package was fixed to use node production mode. Usually this doesn't really do much, but at least the warning is gone.

[sparkwise]

@nebulon I see. Thank you!