PROCEED-Labs / proceed

Business Process Management System
MIT License
5 stars 9 forks source link

Use .env files #218

Closed OhKai closed 7 months ago

OhKai commented 10 months ago

Is your feature request related to a problem? Please describe. By not relying on the old MS API anymore, we should be able to get rid of the forked environments repo and use .env files for dev and prod instead.

While it would be possible to read some env variables during next build, I think it almost always makes more sense to have those be set during runtime with a secret .env that is distributed either manually through us or automatically through something like Google secrets manager. Otherwise we would potentially need many different prod builds for staging / app / 3rd party etc.