maintainBrowserTab configuration option about apiko

[ilabacheuski]

Since apiko is node application why not to use NODE_ENV?
And it can be accessed by process.env
Simple and common practic: Express, Sequelize-CLI

[kasp1]

What could the startup command (apiko run <environment>) look like if we used process.env? How would it work?

[ilabacheuski]

Setting NODE_ENV:

linux & mac: export NODE_ENV=production
windows CMD (not PS!): set NODE_ENV=production

Production: apiko run
Development set NODE=development && apiko run
Testingset NODE=test && apiko run something like it. And for cross-platform setting there is plugin cross-env
So the deployment option is stored in user environment variable NODE_ENV(we can name it differently of course). And in CLI you just access it by process.env.NAME_OF_NEEDED_VARIABLE

[kasp1]

Okay, let's keep it in mind. We'll still have this option in the config though, right?

[ilabacheuski]

Yeah. If we need it. In Production you don't need this option at all. That's why NODE_ENV is usually used.
In package.json is possible to have scripts run, dev, test and so on.

[kasp1]

I realized that if someone runs apiko setup <project_directory> then the starter template is downloaded and it always contains the starter configuration where dev is always the development environment and that gets start up.

Theoretically we could open the browser tab just for the apiko setup <...> command. Just for the newbies so they don't get confused about no UI appearing. This way we could implement it in the CLI tool.

Thinking...