search

bigcommerce / widget-builder

MIT License
18 stars 39 forks source link

Handle multiple environments #126

Open lumo10 opened 1 year ago

lumo10 commented 1 year ago

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 commented 1 year ago

Fantastic idea.

matt-bailey commented 1 year ago

Yes, we need this too.

harnerdesigns commented 1 year ago

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 commented 1 year ago

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 commented 5 months ago

We need this 👍🏽