local.env.js for multiple enviroments/deploys

[gintsgints]

As I understund local.env.js is used when build fullstack app into dist folder.
Does that mean I cannot distribute already built app (in dist folder) to different site?

[JaKXz]

I think this discussion was had in #429 - the generated ./dist folder is a deployable node.js app, and you should be able to add new remotes as necessary.

Did that answer your question @gintsgints? Or am I missing what you mean?

[gintsgints]

Question you mention is related. Because it talks about situation with multiple remotes. But with same local.env.js for all remotes, it will never work. (in local.env.js DOMAIN variable is stored, witch is different for different remotes)

[gintsgints]

Sounds like my wories is clarified in
#513 (comment)
enviroment should be set at remote host itself, not using local.env.js file.

[kingcody]

That is, if you are not using grunt to serve your app. If you are using grunt it will run local.env.js for you. If you required local.env.js in the main server file(app.js) it would set the variables for you without needing grunt. Just wanted to make sure that was understood.

[gintsgints]

Clear. If I use grunt, to start app.. it will use local.env.
But I do not like fact that grunt is needed to start my server at deployment machine.

[DaftMonk]

@gintsgints Grunt is not needed to start your server on a deployment machine. You can start it as a normal node process as long as you run it with the required environment variables.

[gintsgints]

Yeah... enviroment variables is way to go. Thanks.