Hide Forgot
Description of problem: since the environment variable changed from 'APP' to 'GEAR', the README file in github should be changed correspondingly. Version-Release number of selected component (if applicable): https://github.com/openshift How reproducible: always Steps to Reproduce: 1.visit https://github.com/openshift via web browser 2.check the README files for all the examples 3. Actual results: environment variables in README files are still 'OPENSHIFT_APP' Expected results: env variables should be changed to 'OPENSHIFT_GEAR' Additional info: need to be fixed files list: openshift-twt-mongo-demo / README dancer-example / README phpbb-example / README cakephp-example / README django-example / README flask-example / README frogcms-example / README joomla-example / README reviewboard-example / README sinatra-example / README wolfcms-example / README wordpress-example / README bottle-openshift-quickstart / README ciphp / README elgg-openshift-quickstart / README magento-example / README phpmongotweet-example / README kitchensink-example / README kitchensink-html5-mobile-example / README tweetstream-example / environment-readme.txt
This can't be changed until the release is public.
*** Bug 803393 has been marked as a duplicate of this bug. ***
*** Bug 803401 has been marked as a duplicate of this bug. ***
*** Bug 803413 has been marked as a duplicate of this bug. ***
*** Bug 803417 has been marked as a duplicate of this bug. ***
Since some examples will get failed when push without changing the env vars. Need also change the env vars in the github example's code. like twt-mongo-demo
Lower the priority since it needs to wait for release to production
Went a different route. The only variable left that doesn't still exist that end users might use is OPENSHIFT_APP_TYPE and none of the samples use it.
Still can get old env_var like 'OPENSHIFT_APP_DIR' in README files. And found the modified date of the github examples are many days ago.
Fixed readmes and 1 reference to APP_UUID
verified on latest github site, this issue has been fixed.