Every OpenShift application has an associated remote Git repository. When you push the source code to an application gear using git push
, you are pushing the source code to a Git remote named origin
and branch named master
. Every application is configured to autodeploy when code is pushed to the master branch on a remote origin. But it might so happen that you would like to use the master branch for development while using the production branch for deployment. In this recipe, you will learn how to configure an OpenShift application, where you will use a branch named production
for deployment and a master for development.
OpenShift Cookbook
By :
OpenShift Cookbook
By:
Overview of this book
Table of Contents (19 chapters)
OpenShift Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Getting Started with OpenShift
Managing Domains
Creating and Managing Applications
Using MySQL with OpenShift Applications
Using PostgreSQL with OpenShift Applications
Using MongoDB and Third-party Database Cartridges with OpenShift Applications
OpenShift for Java Developers
OpenShift for Python Developers
OpenShift for Node.js Developers
Continuous Integration for OpenShift Applications
Logging and Scaling Your OpenShift Applications
Running OpenShift on a Virtual Machine
Index
Customer Reviews