Handle multiple environments

[lumo10]

Is it possible to enhance the .env file to support multiple environments (prod, stage, dev for example) so that I can choose which environment to publish the widget to? in this case the widget.yml will contain a list of IDs, one for each environment, and I won't have to change it manually every time.

Thank you

[Bobspadger]

Fantastic idea.

[matt-bailey]

Yes, we need this too.

[harnerdesigns]

Throwing another 👍️ for support. This would be super helpful.

Right now I just keep .env, .env.staging, & .env.prod files in the widget folder root. and then widget.yml, widget.staging.yml, & widget.prod.yml files for each widget. Then when I need to push to production, I just copy and paste the values for the .prod files to their appropriate place.

[Bobspadger]

Throwing another 👍️ for support. This would be super helpful.

Right now I just keep .env, .env.staging, & .env.prod files in the widget folder root. and then widget.yml, widget.staging.yml, & widget.prod.yml files for each widget. Then when I need to push to production, I just copy and paste the values for the .prod files to their appropriate place.

Yep same here, works but a bit of a pain to manage.

[josereyes52]

We need this 👍🏽