The OpenShift Team is happy to announce that a new version of OpenShift Online is now available! As always, to make sure everyone is able to take full advantage of any new features, please update to the most recent version of your client tools.
Custom Environment Variables
One of our most requested features is now ready to be used! Prior to today, most people were creating environment variables inside their git repos and the .openshift/action_hooks/ directory. This was cumbersome and difficult for variables that were security sensitive. Now, users can create env vars via the client tools:
rhc env set MYAPP_AUTH_TOKEN='secret' --app myapp
On the topic of environment variables, a request from the user forums has been added regarding JAVA_OPTS. There is now a simple facility to append options to JAVA_OPTS without having to overwrite the entire variable using JAVA_OPTS_EXT. In addition, you can now overwrite options that already exist without them being listed twice:
rhc env set JAVA_OPTS_EXT='-DDEBUG=5' --app myapp
Disk Quota Warnings
In an effort to make disk quota usage more available to users, we have added additional output to actions like logging in or when interacting with the API. Users that are at dangerous levels of disk quota usage will be better informed now and in the future.
PHP PEAR executables in $PATH
We’ve included some bug fixes into this release. PHP PEAR users will note that it now properly works with Jenkins. Additionally, PEAR executables are included in a user’s $PATH which should make using them much easier.
Cartridge Enhancements, PostGIS, Official Python-2.7 Support
As part of our ongoing cartridge work, we’ve updated some of our versions to be a better representation of what users will actually get. This should make it easier to work with minor version upgrades going forward.
PostGIS users will be happy that we now have PostGIS support with Postgres 9.2. Additionally we are moving from the community Python-2.7 cartridge to one that is officially supported. We are working hard to make sure no applications break.
If users had manually installed packages in their virtualenv, they might have to reinstall those packages.