Skip to content
This repository

Public open source repository for the OpenShift client tools and the 'rhc' gem.

branch: master
Octocat-spinner-32 autocomplete Bug 1086138: Show info message when there are no members, reformat me… April 10, 2014
Octocat-spinner-32 bin Readded support to option as array on commander, rhc env spec tests f… September 02, 2013
Octocat-spinner-32 conf express.conf: Terminate last line with newline October 16, 2013
Octocat-spinner-32 cucumber Fix cucumber support script: Pick user_register_script_format based o… April 11, 2014
Octocat-spinner-32 features Fixes failing test in rhc/features/core_feature.rb:178 March 27, 2014
Octocat-spinner-32 lib Skip forking output for jruby April 17, 2014
Octocat-spinner-32 man man: updating the rhc manual page and cleaning it up November 26, 2013
Octocat-spinner-32 rel-eng Automatic commit of package [rhc] release [1.23.6-1]. April 17, 2014
Octocat-spinner-32 spec Improve message when searching member teams April 14, 2014
Octocat-spinner-32 tasks Origin UI 72 - Memberhip September 26, 2013
Octocat-spinner-32 .gitignore Merge remote-tracking branch 'origin/master' into avoid_creating_conf… October 19, 2012
Octocat-spinner-32 .rspec Upgrade spec tests to passing, fix RSpec2 syntax errors, ensure rando… March 29, 2013
Octocat-spinner-32 .travis.yml Bug 1048392 - remove workaround for travis CI failures January 27, 2014
Octocat-spinner-32 .vimrc Added .vimrc for coding standards and updated README so people know h… April 27, 2012
Octocat-spinner-32 COPYRIGHT Move everything in express/ into the root June 24, 2012
Octocat-spinner-32 Gemfile Latest version of rake breaks bundle install on ruby 1.8.x March 27, 2014
Octocat-spinner-32 LICENSE Move everything in express/ into the root June 24, 2012
Octocat-spinner-32 Removed references to OpenShift forums in several places February 05, 2014
Octocat-spinner-32 Rakefile Move everything in express/ into the root June 24, 2012
Octocat-spinner-32 Bug 994986 - Remove 'rhc cartridge' because it conflicts with other a… August 20, 2013
Octocat-spinner-32 client.spec Automatic commit of package [rhc] release [1.23.6-1]. April 17, 2014
Octocat-spinner-32 rhc.gemspec adding rhc scp command for transferring files to and from gears, alon… October 19, 2013

OpenShift Command Line Tools (RHC) Build Status

The OpenShift command line tools allow you to manage your OpenShift applications from the command line. The Getting Started guide has additional info on installing the tool on each supported operating system.

Please stop by #openshift on if you have any questions or comments. For more information about OpenShift, visit or the OpenShift support page

Using RHC to create an application


  • git
  • openssh-clients
  • ruby (1.8.7 or later)
  • rubygems

Step 1: Run the setup command to configure your system:

$ rhc setup

Follow the instructions in setup to set your SSH keys and create a domain. The name you choose for your domain will form part of your application's public URL.

Step 2: Create an OpenShift application:

$ rhc app create -a appname -r /path/to/new/git/repo -t <framework Ex: php-5.3>

Once that's complete, follow the directions printed at the end of running rhc app create.

Making changes to your application

Once your site is created, updating it is as simple as making changes to your git repo. Commit them, then push. For example:

$ edit index.php
$ git commit -a -m "what I did"
$ git push

Then just reload your web page to see the changes.

OS X Notes:

git: OS X 10.6 comes w/ ssh and ruby, but not with git, unless you have Xcode 4.0.x installed (as a developer you should have Xcode anyway). Xcode, however, is not free (unless you are a registered Apple Developer) and costs around $5 from the Apple App Store.

If you do not have Xcode, you can obtain a pre-packaged version of git from:

Installing git from MacPorts/HomeBrew/Fink/etc requires Xcode.

Now obtain the client code, either via 'git clone' as above or via the rhc gem.

Developing / Contributing

We expect code contributions to follow these standards:

  1. Ensure code matches the GitHub Ruby styleguide, except where the file establishes a different standard.
  2. We use RSpec for functional testing and Cucumber for our high level integration tests. Specs are in 'spec/' and can be run with bundle exec rake spec. Features are in 'features/' and can be run with bundle exec rake features (although these tests runs against the gem installed locally so you will need to gem install first). See in the features dir for more info.
  3. We maintain 100% line coverage of all newly added code via spec testing. The build will fail if new code is added and it does not have full line coverage. Some old code is currently excluded until it can be refactored. Run bundle exec rake spec on Ruby 1.9+ to see your code coverage level.
  4. When writting a new Command please follow

Once you've made your changes:

  1. Fork the code
  2. Create a topic branch - git checkout -b my_branch
  3. Push to your branch - git push origin my_branch
  4. Create a Pull Request from your branch
  5. That's it!

If you use vim, we've included a .vimrc in the root of this project. In order to use it, install

Something went wrong with that request. Please try again.