Managing Environment Variables about lightning-cli HOT 6 CLOSED

#50

from lightning-cli.

@mattiapontonio, thank you for reply.

In my case, I have two different API endpoints (test, prod)
For instance, when I'm running 'lng dev' command, the dist folder is being created, and local server launches.
But It would be nice to pass a local variable that indicates whether to use prod URL or DEV URL
instead of each time manually change URL value before building dist folder

from lightning-cli.

I agree. But as mention in the comment lng dev is just a "bonus". You can simply build and serve the folder via Your own Node server with your configs.

#50 (comment)

Side note: serving the app Is not mandatory that is served from the same server of the API so this is a Front End issue managable via some configs file. Is not a CLI serving issue, Is a build issue relative to the files that your are going to build. I think.

from lightning-cli.

There are some plans to implement environment variables, that could come in handy for these type of cases. It's currently in local development. No ETA yet.

from lightning-cli.

A quick and easy solution could be spread [options] from CLI process using argv to the http-server directly.

from lightning-cli.

Support for environment variables are added in Lightning-CLI v1.7.0
https://github.com/rdkcentral/Lightning-CLI#environment-variables

from lightning-cli.