You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<%=vars.product_short%> lets you externalize configuration - storing application properties in <ahref="../devguide/deploy-apps/environment-variable.html" target="_blank">environment variables</a>.
At runtime, environment variables are exposed to the application through its environment. You can use this for example to run your app in production mode setting the `APP_MODE` environment variable.
<preclass="terminal">
$ cf set-env my-java-app APP_MODE production
Setting env variable 'APP_MODE' to 'production' for app my-java-app in org MyOrg / space MySpace as user@smydomain.com...
OK
TIP: Use 'cf restage' to ensure your env variable changes take effect
</pre>
Then restage your app as suggested using
<preclass="terminal">
$ cf restage my-java-app
Restaging app my-java-app in org MyOrg / space MySpace as user@mydomain.com...
-----> Downloaded app package (3M)
...
</pre>
All environment variables can be accessed using `System.getenv().get('ENV_VARIABLE')` or `new ProcessBuilder().environment().get("ENV_VARIABLE")` from within your Java app.
<divstyle="text-align:center;margin:3em;">
<ahref="./bind-service.html" class="btn btn-primary">I've set my environment variable</a>