Custom extension (node) Set or change .env variable module

[Hyperbytes]

This is a simple module to manage .ENV variables.

With this extension you can change .ENV variable values, create new .ENV variables or simply return the value of an existing .ENV variable

@hyperbytes/wappler-get-or-set-environment-value

Install as per these instructions.

How To Install and Use Custom Wappler Extensions

Intro Wappler’s extensibility options allow you to create custom extensions for both Server Connect and App Connect. Wappler has an easy to use UI, to install custom extensions published on npm and github. Installing Custom Extensions The extensions you install in Wappler are installed per project, so you need to add them to every project you need to use them. Open the Project Settings: [Screenshot_1] And click Extensions: [Screenshot_2] Here you can find a list of all the extensions i…

DONT FORGET A WAPPLER RESTART AFTER INSTALL

Once installed the use will see a new server connect group called "Environment"

within this group you will see:

Add the component:

Enter the mandatory environment variable name, i enter "MY_NAME"

.ENV variables should be declared in CAPITALS, the module will force any name entered into capitals unless the "Allow Mixed case" checkbox is checked.

Next add a value, i add my name, "Brian English"

Lastly check "Output" if you wish to see the result

On running the API action, the module performs the following actions:

1. if the .ENV variable exists and no value is sent from the module, it simply returns the current value
2. If the .ENV variable exists and a value is sent, it's value is changed
3. If the .ENV variable does not exist, it is created and it's value set

On this case the .ENV variable MY_NAME is created and given the value of "Brian English".
In all cases the module returns the current value of the .ENV variable in exit

{"Env1":"Brian English"}

NOTE. These changes are not written to app/config/config.json, they are dynamic in nature.

Changes will be lost, default values restored and new variables cleared on server start

[sid]

Hi Brian.
ENV variables are by nature not supposed to be set from the code - they should only be used in the code - from what my understanding is.
What would be the use case for creating ENV variables or changing its values in runtime?

[Hyperbytes]

Ask jim

Best practice to store api keys

Hi, Its the first time i have used a external api. I am using a external api that has a clientid(never changes), apikey(need to be changed every 90 days), email(never changes) and bearer token (changes every 30 mins). To get a bearer token and api key change this can be done by the api. I'm currently storing them in environment variables. Is this best practice? Can i update the environment variables without changing them in the settings tab? Should i be saving them somewere else. Projects on…

[sid]

Ah! Sorry to say but your help here is promoting bad coding practice.

Storing things like these in the DB is the best practice - as suggested on the post.
Or even in a file on the server, and read/write data from file - this would require custom extensions though.

[Hyperbytes]

I call it enabling choice.