红帽全球峰会此内容没有您所选择的语言版本。
Chapter 2. Application Life Cycle Examples
2.1. Overview
As a PaaS, OpenShift Enterprise is designed for building and deploying applications. Depending on how much you want to involve OpenShift Enterprise in the development process, you can choose to develop on OpenShift Enterprise and use it to continuously develop an application, or you can deploy a fully developed application onto an OpenShift Enterprise instance.
2.2. Developing on OpenShift Enterprise
You can develop your application on OpenShift Enterprise directly. Use the following process if you plan to use OpenShift Enterprise as a method to build and deploy your application:
- Initial Planning
- What does your application do?
- What programming language will it be developed in?
- Access to OpenShift Enterprise
- OpenShift Enterprise should be installed by this point, either by yourself or an administrator within your organization.
- Develop
- Using your editor/IDE of choice, create a basic skeleton of an application. It should be developed enough to tell OpenShift Enterprise what kind of application it is.
- Push the code to your Git repository.
- Generate
-
Create a basic application using the
new-appcommand. OpenShift Enterprise generates build and deployment configurations.
-
Create a basic application using the
- Manage
- Start developing your application code.
- Ensure your application builds successfully.
- Continue to locally develop and polish your code.
- Push your code to a Git repository.
- Is any extra configuration needed? Explore the Developer Guide for more options.
- Verify
-
You can verify your application in a number of ways. You can push your changes to your application’s Git repository, and use OpenShift Enterprise to rebuild and redeploy your application. Alternatively, you can hot deploy using
rsyncto synchronize your code changes into a running pod.
-
You can verify your application in a number of ways. You can push your changes to your application’s Git repository, and use OpenShift Enterprise to rebuild and redeploy your application. Alternatively, you can hot deploy using
2.3. Developing Then Deploying on OpenShift Enterprise
Another possible application life cycle is to develop locally, then use OpenShift Enterprise to deploy your fully developed application. Use the following process if you plan to have application code already, then want to build and deploy onto an OpenShift Enterprise installation when completed:
- Initial Planning
- What does your application do?
- What programming language will it be developed in?
- Develop
- Develop your application code using your editor/IDE of choice.
- Build and test your application code locally.
- Push your code to a Git repository.
- Access to OpenShift Enterprise
- OpenShift Enterprise should be installed by this point, either by yourself or an administrator within your organization.
- Generate
-
Create a basic application using the
new-appcommand. OpenShift Enterprise generates build and deployment configurations.
-
Create a basic application using the
- Verify
- Ensure that the application that you have built and deployed in the above Generate step is successfully running on OpenShift Enterprise.
- Manage
- Continue to develop your application code until you are happy with the results.
- Rebuild your application in OpenShift Enterprise to accept any newly pushed code.
- Is any extra configuration needed? Explore the Developer Guide for more options.
