Cloud
Configuration via environment variables only works for apps with a dynamic backend. But what if we want to configure a front-end app?
The 12 factor manifest(opens in new tab) tells us in point III that apps should retrieve their config from environment variables to strictly separate config from code. “Config” meaning everything that is likely to vary between deployments (staging, production, developer environments, etc). Cloud Foundry allows us to do that very easily using either the manifest.yml file or the cf set-env command. However, this only works for apps which have a dynamic back end. What if we want to configure a front end app that we have pushed to Cloud Foundry using the staticfile buildpack(opens in new tab)? These apps are, by definition, static so they cannot read out any environment variables. Therefore, if we use this buildpack to deploy an Angular or React app, we cannot use these variables.
To learn how to solve this problem, check out the post on my personal blog at bespinian.io(opens in new tab).
Software- and Cloud Engineer
Find the job or career to suit you. A career where you can make a difference and continue your personal development.
What you do is who we are.
