Let's suppose you are a system administrator of your organization, where your job is to make sure all the production applications are running smoothly. Ideally, you would not want all the developers in your organization to have access to the production environment. Giving everyone access to the production environment is waiting for the inevitable to happen. What you should remember is that you can have different domains for different environments. The domain corresponding to the production deployment will be controlled by system administrators rather than developers. OpenShift allows you to give different access levels to a different group of people. You, along with other system administrators, can enjoy admin access to the production domain, whereas developers can only have viewer access, if required. Developers will be added to the production domain in the read-only mode. They can view the information about it and its applications, but they cannot...
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