Hi, i am running Node-RED on Ubuntu. In a bash script i export a variable like this: export TEST=TEST or export TEST=TEST >> ~/.bashrc when i typ printenv in de commandline i can see the variable is set JOURNAL_STREAM=9:45470 XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/li…

How are you running Node-RED ? Is it in the same session you set that variable in ?

Yes, Node-RED is running locally the bash script and Node-RED installation is running in the same session/user. But it is not only the custom exported environment variabel that has a empty payload result but also for example the by default set "$GDMSESSION " variable is empty

How are you starting node-red after checking printenv in the command line?

i have set sudo systemctl enable nodered.service if that's what you mean

So node red is not running the same session where you are checking the environment. It is running in a systemd session. Those environment variables are probably not set in that environment. For example GDMSESSION will not be set because node-red does not have a display attached. Similarly .bash…

so yes Node-RED is already running so it's environment has been set when it started. Any variables set after starting won't be updated. If you do a node-red-stop to stop that - then set your variable then just node-red (not node-red-start) - so it's started in the local environment it should then re…

[image] coen17st: Can someone explain how node-RED handles the system $ environmental variables? Some good insights in this previous discussion. [image] How to set env variable General @DemonKing environment variables are only evaluated when flows are started. The …

If you need to be able to specify environment variables for Node-RED, you can easily do so by tweaking the systemd service file. You will find examples in alternate-node-red-installer which I am, in fact, just updating. You can provide an environment file as well which will be easier to amend if yo…

[image] dceejay: so yes Node-RED is already running so it's environment has been set when it started. Any variables set after starting won't be updated. If you do a node-red-stop to stop that - then set your variable then just node-red (not node-red-start) - so it's started in the local environm…

I've just pushed some changes to GitHub so do have a look at the version there. The whole repo is a bit rough and ready but it at least points the way.

Node-RED

Node-RED Forum

System $ environmental variables empty result

General

Andrei 29 December 2020 16:31 8

Some good insights in this previous discussion.

Topic		Replies	Views
Accessing environment variables General	16	462	2 April 2024
Report import of EnvironmentFile in Node-red console / log Feature Requests linux	7	69	20 September 2024
Reading user environment variables General	3	795	12 May 2021
Using environment variables General	15	348	27 October 2023
Is there a way to externalize mongodb connection info General	26	1657	28 December 2019

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

System $ environmental variables empty result

Related topics