"PhpStorm is a lightweight and smart PHP IDE focused on developer productivity that deeply understands your code, provides smart code completion, quick navigation and on-the-fly error checking. It is always ready to help you shape your code, run unit-tests or provide visual debugging." In this tutorial I will show you how to use build in functionality in PhpStorm to deploy PHP application to OpenShift.

Screenshots are included in the post to guide you through the process - creating a new project, setting up the SFTP configuration and where to go to upload the changes to your system to OpenShift.

I considered Amazon, Orchestra.io, and a few others, but was concerned about the idea of a ~$50/month cost for something I'm uncertain about. When I asked in #zftalk.dev, someone suggested OpenShift as an idea, and coincidentally, the very next day Zend announced a partnership with RedHat surrounding OpenShift. The stars were in alignment. In the past month, in the few spare moments I've had (which included an excellent OpenShift hackathon at ZendCon), I've created a quick application that I've deployed and tested in OpenShift. These are my findings.

He talks about getting a Zend Framework 2 application up and running with a few changes to the default directory structure they provide. He also talks about using Composer as a deploy task. He mentions a few of the tricks to watch out for as you're deploying your app and some of the "good parts" he found about the product and experience (like being able to use CNAMEs and having SSH access to the instance by default.

In this blog post, I am going to show you how to get up and running with CodeIgniter and MongoDB. Best of all, I will show you how to get all of this deployed to a fully scalable environment using OpenShift from Red Hat.

The process involves:

• Creating an OpenShift account
• Installing the RHC client tools
• Creating an OpenShift application
• Adding mongodb to your application
• Adding mongodb support to CodeIgniter
• Creating a Model, View, and Controller
• Deploy and test your application

You can then SSH into the instance and look at the database to call a "find()" and see what's there.