diff --git a/client_tools_install_guide/configuring_client_tools.adoc b/client_tools_install_guide/configuring_client_tools.adoc new file mode 100644 index 000000000000..b7cfcf98d57a --- /dev/null +++ b/client_tools_install_guide/configuring_client_tools.adoc @@ -0,0 +1,172 @@ +[[Configuring_Client_Tools]] += Configuring Client Tools + +After the client tools are installed, they must be configured. The easiest method of configuring the client tools is to use the interactive setup wizard, which walks you through the configuration steps by asking several questions. + + +[IMPORTANT] +==== +You must run the interactive setup wizard after installing the client tools so that your workstation is correctly configured to communicate with the remote OpenShift server. +==== + +The following is a sample walk through of the setup wizard, and some general information to assist you with the initial configuration. It assumes you have installed the latest version of the client tools. Use +rhc --version+ to verify the installed version, or link:Updating_Client_Tools.html[update the client tools]. + + +[NOTE] +==== +The following setup wizard example was run on Windows 7. Screen outputs may vary depending on the operating system. +==== + + +*Starting the Setup Wizard* + +Launch the setup wizard: +---- +$ rhc setup +OpenShift Client Tools (RHC) Setup Wizard + +This wizard will help you upload your SSH keys, set your application namespace, and check that other programs like Git are properly installed. +---- + +*Login Information* + +The setup wizard next prompts you for the login credentials that were used to sign up for an OpenShift account. Alternatively, you can also use your Red Hat login credentials. +---- +Login to openshift.redhat.com: user@example.com +Password: password +---- + +*Authorization Tokens* + +You are then prompted to generate an authorization token. Answering _++yes++_ will store a token in your home directory to be used on subsequent requests. When it expires, you are prompted for your password again. + + + +---- +OpenShift can create and store a token on disk which allows to you to access the server without using your password. The key is stored in your home directory and should be kept secret. You can delete the key at any time by running 'rhc logout'. +Generate a token now? (yes|no) yes +Generating an authorization token for this client ... lasts about 1 day +---- + +*Configuration File* + +With your login credentials, the setup wizard creates the *express.conf* configuration file in your home directory. In the following example, the *express.conf* file is created in the *C:\Users\User1\.openshift* directory. +---- + +Saving configuration to C:\Users\User1\.openshift\express.conf ... done + +---- + + + + + +*SSH Keys* + +Next, the setup wizard configures the SSH keys so that your system can authenticate with the remote server. Because this is the initial configuration, it is assumed no existing SSH keys are found on your system. Therefore, the setup wizard generates a new pair of SSH keys, named *id_rsa* and *id_rsa.pub*, and saves them in your home directory. In the following example the SSH keys are generated and saved in the *C:\Users\User1\.ssh* directory. +---- + +No SSH keys were found. We will generate a pair of keys for you. +Created: C:\Users\User1\.ssh\id_rsa.pub + +---- + +After the new SSH keys are generated, the public key, *id_rsa.pub*, must be uploaded to the OpenShift server to authenticate your system to the remote server. Enter a name to use for your key, or leave it blank to use the default name. In the following example the default name is used. +---- +Your public ssh key must be uploaded to the OpenShift server to access code. +Upload now? (yes|no) yes + +Since you do not have any keys associated with your OpenShift account, your new key will be uploaded as the 'default' key + +Uploading key 'default' from C:\Users\User1\.ssh\id_rsa.pub ... done +---- + + + + + +*Installed Software* + +The setup wizard verifies if Git version control software is installed on your system. Git is required to create and deploy applications to the OpenShift cloud environment. It is assumed that all the required software for your operating system is already installed as described in the earlier sections of this document. In the example below, the setup wizard verifies that Git for Windows is installed correctly. +---- + +In order to fully interact with OpenShift you will need to install and configure a git client if you have not already done so. +Documentation for installing other tools you will need for OpenShift can be found at https://openshift.redhat.com/community/developers/install-the-client-tools + +We recommend these free applications: + + +* Git for Windows - a basic git command line and GUI client https://github.com +/msysgit/msysgit/wiki/InstallMSysGit + +* TortoiseGit - git client that integrates into the file explorer http://code. +google.com/p/tortoisegit/ + +---- + + + + + +*Domain* + +The setup wizard next verifies whether a domain already exists for your cloud environment. The example below assumes that a domain does not exist, and one must be created. If you did create a domain when you signed up for an OpenShift account, it is displayed here. To create a domain at this time, enter the desired name when prompted. Alternatively, you can create a domain using the OpenShift Management Console, or with the +rhc domain create+ command later. The domain named _MyDomain_ is created in the following example. +---- + +Checking for a domain ... none + +Your domain is unique to your account and is the suffix of the public URLs we assign to your applications. You may configure your domain here or leave it blank and use 'rhc domain create' to create a domain later. You will not be able to create applications without first creating a domain. + +Please enter a domain (letters and numbers only) ||: MyDomain +Your domain name 'MyDomain' has been successfully created +---- + + + + + + +[IMPORTANT] +==== +A domain must be created before you can create OpenShift applications. + + +==== + + +*Applications* + + + +Finally, the setup wizard verifies whether any applications exist under your domain. Any applications created with the Management Console are displayed here. In the example below, no applications have been created. In this case the setup wizard shows the types of applications that can be created with the associated commands. The setup wizard then completes by displaying the current gear consumption along with the gear sizes available to the given user. +---- + +Checking for applications ... none + +Run 'rhc app create' to create your first application. + + Do-It-Yourself rhc app create diy-0.1 + JBoss Application Server 7.1 rhc app create jbossas-7 + JBoss Enterprise Application Platform 6.0 rhc app create jbosseap-6.0 + Jenkins Server 1.4 rhc app create jenkins-1.4 + Node.js 0.10 rhc app create nodejs-0.10 + PHP 5.3 rhc app create php-5.3 + PHP 5.4 rhc app create php-5.4 + Perl 5.10 rhc app create perl-5.10 + Python 2.6 rhc app create python-2.6 + Python 2.7 Community Cartridge rhc app create python-2.7 + Python 3.3 Community Cartridge rhc app create python-3.3 + Ruby 1.8 rhc app create ruby-1.8 + Ruby 1.9 rhc app create ruby-1.9 + Tomcat 6 (JBoss EWS 1.0) rhc app create jbossews-1.0 + Tomcat 7 (JBoss EWS 2.0) rhc app create jbossews-2.0 + Zend Server 5.6 rhc app create zend-5.6 + + You are using 0 of 3 total gears + The following gear sizes are available to you: small + +Your client tools are now configured. + +---- + +The OpenShift client tools are now configured on your system. \ No newline at end of file diff --git a/client_tools_install_guide/images/2821.png b/client_tools_install_guide/images/2821.png new file mode 100644 index 000000000000..423e89d97fae Binary files /dev/null and b/client_tools_install_guide/images/2821.png differ diff --git a/client_tools_install_guide/images/2823.png b/client_tools_install_guide/images/2823.png new file mode 100644 index 000000000000..f5be0a30315f Binary files /dev/null and b/client_tools_install_guide/images/2823.png differ diff --git a/client_tools_install_guide/images/2826.png b/client_tools_install_guide/images/2826.png new file mode 100644 index 000000000000..6dd28bdd226e Binary files /dev/null and b/client_tools_install_guide/images/2826.png differ diff --git a/client_tools_install_guide/images/2828.png b/client_tools_install_guide/images/2828.png new file mode 100644 index 000000000000..353c7efa5e86 Binary files /dev/null and b/client_tools_install_guide/images/2828.png differ diff --git a/client_tools_install_guide/images/2829.png b/client_tools_install_guide/images/2829.png new file mode 100644 index 000000000000..c39949ec9956 Binary files /dev/null and b/client_tools_install_guide/images/2829.png differ diff --git a/client_tools_install_guide/images/2830.png b/client_tools_install_guide/images/2830.png new file mode 100644 index 000000000000..6061208a382a Binary files /dev/null and b/client_tools_install_guide/images/2830.png differ diff --git a/client_tools_install_guide/images/3265.png b/client_tools_install_guide/images/3265.png new file mode 100644 index 000000000000..d926de193b91 Binary files /dev/null and b/client_tools_install_guide/images/3265.png differ diff --git a/client_tools_install_guide/images/icon.svg b/client_tools_install_guide/images/icon.svg new file mode 100644 index 000000000000..10467e12dd94 --- /dev/null +++ b/client_tools_install_guide/images/icon.svg @@ -0,0 +1,19 @@ + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/client_tools_install_guide/images/icons/caution.png b/client_tools_install_guide/images/icons/caution.png new file mode 100644 index 000000000000..9a8c515a109f Binary files /dev/null and b/client_tools_install_guide/images/icons/caution.png differ diff --git a/client_tools_install_guide/images/icons/example.png b/client_tools_install_guide/images/icons/example.png new file mode 100644 index 000000000000..1199e864f850 Binary files /dev/null and b/client_tools_install_guide/images/icons/example.png differ diff --git a/client_tools_install_guide/images/icons/important.png b/client_tools_install_guide/images/icons/important.png new file mode 100644 index 000000000000..be685cc4ecc7 Binary files /dev/null and b/client_tools_install_guide/images/icons/important.png differ diff --git a/client_tools_install_guide/images/icons/note.png b/client_tools_install_guide/images/icons/note.png new file mode 100644 index 000000000000..f087c73b7aef Binary files /dev/null and b/client_tools_install_guide/images/icons/note.png differ diff --git a/client_tools_install_guide/images/icons/originalnote.png b/client_tools_install_guide/images/icons/originalnote.png new file mode 100644 index 000000000000..7c1f3e2fa7ef Binary files /dev/null and b/client_tools_install_guide/images/icons/originalnote.png differ diff --git a/client_tools_install_guide/images/icons/warning.png b/client_tools_install_guide/images/icons/warning.png new file mode 100644 index 000000000000..d41edb9adbf2 Binary files /dev/null and b/client_tools_install_guide/images/icons/warning.png differ diff --git a/client_tools_install_guide/images/note.png b/client_tools_install_guide/images/note.png new file mode 100644 index 000000000000..f087c73b7aef Binary files /dev/null and b/client_tools_install_guide/images/note.png differ diff --git a/client_tools_install_guide/installing_client_tools_on_fedora.adoc b/client_tools_install_guide/installing_client_tools_on_fedora.adoc new file mode 100644 index 000000000000..4f48695c22a7 --- /dev/null +++ b/client_tools_install_guide/installing_client_tools_on_fedora.adoc @@ -0,0 +1,58 @@ +[[Installing_Client_Tools_on_Fedora]] += Installing Client Tools on Fedora + +The OpenShift client tools are supported on Fedora 16 or later and require sudoer or root access. + +[NOTE] +==== +The +sudo+ command only works if the particular user is listed in the +sudoers+ file. As an alternative to sudo access, you can activate a root terminal with the +su+ command and the root password. If you activate a root terminal, omit +sudo+ from the commands shown in the examples. Be sure to close the root terminal when the installation process is complete. +==== + +You can install the client tools on Fedora operating systems by installing the RPM with the YUM package manager, or by installing the gem. + + +[NOTE] +==== +The RPM version of the client tools is not updated as frequently as the gem maintained by the OpenShift development team. +==== + + + +*Install with YUM Package Manager* + +From the terminal, install the client tools and all other required dependencies: +---- +$ sudo yum install rubygem-rhc +---- + +*Installing with Gem* + +1. From the terminal, install Ruby and RubyGems if they are not already installed: ++ +---- +$ sudo yum install rubygems +---- + +2. Install the client tools and all other required dependencies: ++ +---- +$ sudo gem install rhc +---- + +== Installation Issues and Tips for Fedora + +*Automatic Completion Using the Tab Key* + +The client tools for Fedora support the automatic completion feature of the bash shell. Run the following command and follow the instructions to enable automatic completion: +---- +$ rhc setup --autocomplete +---- + +You may have to close your current terminal session, and open a new session to automatically source the bash completion script. + +If the automatic completion feature is not persistent when you open a new terminal session, the automatic completion script for the client tools must be sourced in the *_.bashrc_* file in your home directory. Do this by adding the following line to to your *_.bashrc_* file: +---- +source /etc/bash_completion.d/rhc +---- + +//When the installation completes, proceed to <> to configure the client tools using the interactive setup wizard. \ No newline at end of file diff --git a/client_tools_install_guide/installing_client_tools_on_macosx.adoc b/client_tools_install_guide/installing_client_tools_on_macosx.adoc new file mode 100644 index 000000000000..0653e3d60fd3 --- /dev/null +++ b/client_tools_install_guide/installing_client_tools_on_macosx.adoc @@ -0,0 +1,57 @@ +[[Installing_Client_Tools_on_Mac_OS_X]] += Installing Client Tools on Mac OS X + +:icons: + +The OpenShift client tools are supported on Mac OS X 10.5 or later and require sudo access. + +Installing the client tools on a Mac OS X operating system comprises three steps: + + +*Step 1*: Install *_Ruby_* + +*Step 2*: Install *_Git_* version control + +*Step 3*: Install the client tools + +== Install Ruby + +Mac OS X Lion ships with Ruby 1.8.7 preinstalled. Previous versions of OS X included Ruby as part of the link:$$https://developer.apple.com/xcode/$$[Xcode] integrated development environment. If you are installing the client tools on a version of OS X that did not ship with Ruby preinstalled, you can install it one of two ways: + +* Use the OS X installation CD + + +* Download and install the link:$$https://developer.apple.com/xcode/$$[Xcode] integrated development environment from the Apple website + +Alternatively, if you are experienced with Mac OS software development, you can also: + + +* Download and install Ruby from the link:$$http://macruby.org/$$[MacRuby] website, or + + +* Visit link:$$http://www.ruby-lang.org/en/downloads/$$[] for help installing Ruby with homebrew + +After Ruby is installed, run the following command to verify that it has installed correctly: +---- +$ ruby -e 'puts "Welcome to Ruby"' +Welcome to Ruby +---- + +== Install Git Version Control + +Although there are a number of options available to install Git version control on Mac OS X, Red Hat recommends to download and install the latest version from here: link:$$http://code.google.com/p/git-osx-installer/$$[]. + +When the installation completes,, run the following command to verify that Git has installed correctly: +---- +$ git --version +---- + +This command returns the Git version number that was installed. + +== Install the Client Tools + +When Ruby and Git have been successfully installed, run the following command to install the client tools: +---- +$ sudo gem install rhc +---- +//When the installation completes, proceed to <> to configure the client tools using the interactive setup wizard. diff --git a/client_tools_install_guide/installing_client_tools_on_opensuse.adoc b/client_tools_install_guide/installing_client_tools_on_opensuse.adoc new file mode 100644 index 000000000000..28cafefdaac1 --- /dev/null +++ b/client_tools_install_guide/installing_client_tools_on_opensuse.adoc @@ -0,0 +1,72 @@ +[[Installing_Client_Tools_on_openSUSE]] += Installing Client Tools on openSUSE + +:icons: + +Installing the client tools on openSUSE requires sudoer or root access and comprises three steps: + +*Step 1*: Install *_Ruby_* + + +*Step 2*: Install *_RubyGems_* + + +*Step 3*: Install *_Git_* + +*Step 4*: Install the client tools + + + + +[NOTE] +==== +The +sudo+ command only works if the particular user is listed in the _sudoers_ file. As an alternative to sudo access, you can activate a root terminal with the +su+ command and the root password. If you activate a root terminal, omit +sudo+ from the commands shown in the examples. Be sure to close the root terminal after the installation completes. +==== + +== Install Ruby + +From terminal, run the following command to install Ruby: +---- +$ sudo zypper install ruby +---- + +Run the following command to verify that Ruby has installed correctly: +---- +$ ruby -e 'puts "Welcome to Ruby"' +Welcome to Ruby +---- + + + + +== Install RubyGems + +Run the following command to install RubyGems: +---- +$ sudo zypper install rubygems +---- + +== Install Git + +Run the following command to install Git version control: +---- +$ sudo zypper install git-core +---- + +After installation completes, run the following command to verify that Git has installed correctly: +---- +$ git --version +git version 1.7.11.1 +---- + +This command returns the Git version number that was installed. + + +== Install the Client Tools + +When the required software has been successfully installed, run the following command to install the client tools: +---- +$ sudo gem install rhc +---- + +//When the installation completes, proceed to <> to configure the client tools using the interactive setup wizard. \ No newline at end of file diff --git a/client_tools_install_guide/installing_client_tools_on_rhel.adoc b/client_tools_install_guide/installing_client_tools_on_rhel.adoc new file mode 100644 index 000000000000..e8fdcd3eb125 --- /dev/null +++ b/client_tools_install_guide/installing_client_tools_on_rhel.adoc @@ -0,0 +1,96 @@ +[[Installing_Client_Tools_on_RHEL]] += Installing Client Tools on Red Hat Enterprise Linux + +You must have the following to successfully install the client tools: + +* Red Hat Enterprise Linux 6 or later +* Sudoer or root access +* Ruby and RubyGems installed (including rubygem-json and rubygem-parseconfig) + + +[NOTE] +==== +The +sudo+ command only works if the particular user is listed in the *_sudoers_* file. As an alternative to sudo access, you can activate a root terminal with the +su+ command and the root password. If you activate a root terminal, omit +sudo+ from the commands shown in the examples. Be sure to close the root terminal after the installation completes. +==== + +=== Installing RubyGems + +If the RubyGems package is not already installed, you must enable the Red Hat Enterprise Linux optional repository channel. The RubyGems package dependencies are then automatically resolved when the client tools are installed. + +If you are using the Certificate-Based Red Hat Network (RHN) tooling, use the following command to enable the optional channel: +---- +$ sudo yum-config-manager --enable [architecture][operating_system]-optional-6 +---- + + + +If you are using the classic RHN subscription, use the following command to enable the optional channel: +---- +$ sudo rhn-channel --add --channel=[architecture]-[operating_system]-optional-6 +---- + + +* _++architecture++_: your system architecture. Enter either _i386_ or *x86_64*. + + +* _++operating system++_: type of operating system installed. Enter either _workstation_ or _server_. + + + +For example, if you have Red Hat Enterprise Linux Workstation 6 or later installed on a 64-bit x86 computer, and you are using the classic Red Hat Network subscription, run the following command to enable the optional repository: +---- +$ sudo rhn-channel --add --channel=rhel-x86_64-workstation-optional-6 +---- + +=== Installing Client Tools + +Ensure that the RubyGems software package is installed on your system. Otherwise, the optional repository channel must be enabled on systems that are registered on RHN. + +Run the following command to install the client tools: +---- +$ sudo gem install rhc +---- + + + +Update client tools to the latest version: + +---- +$ sudo gem update rhc +---- + +The following example shows a typical installation on a Red Hat Enterprise Linux operating system. Some information has been removed for clarification purposes. + +.Installation Process on Red Hat Operating System +==== +---- +Installation Process on Red Hat Operating System +$ sudo gem install rhc +Freeing read locks for locker 0x1: 2360/140216412567296 +........ +Resolving Dependencies +--> Running transaction check +........ + +Complete! +---- +==== + +=== Installation Issues and Tips + + +*Automatic Completion Using the Tab Key* + +The OpenShift client tools for Red Hat Enterprise Linux support the automatic completion feature of the bash shell. Run the following command and follow the instructions to enable automatic completion: +---- +$ rhc setup --autocomplete +---- + +You may have to close your current terminal session, and open a new session to automatically source the bash completion script. + +If the automatic completion feature is not persistent when you open a new terminal session, the automatic completion script for the client tools must be sourced in the *_.bashrc_* file in your home directory. Do this by adding the following line to to your *_.bashrc_* file: +---- +source /etc/bash_completion.d/rhc +---- + +//When the installation completes, proceed to <> to configure the client tools using the interactive setup wizard. \ No newline at end of file diff --git a/client_tools_install_guide/installing_client_tools_on_ubuntu_debian.adoc b/client_tools_install_guide/installing_client_tools_on_ubuntu_debian.adoc new file mode 100644 index 000000000000..c8b02902670d --- /dev/null +++ b/client_tools_install_guide/installing_client_tools_on_ubuntu_debian.adoc @@ -0,0 +1,91 @@ +[[Installing_Client_Tools_on_Ubuntu_and_Debian]] += Installing Client Tools on Ubuntu and Debian + +:icons: + +Installing the client tools on Ubuntu or Debian requires sudoer or root access and comprises four steps: + +*Step 1*: Install *_Ruby_* + +*Step 2*: Install *_RubyGems_* + +*Step 3*: Install *_Git_* + +*Step 4*: Install the client tools + +[NOTE] +==== +The +sudo+ command only works if the particular user is listed in the _sudoers_ file. As an alternative to sudo access, you can activate a root terminal with the +su+ command and the root password. If you activate a root terminal, omit +sudo+ from the commands shown in the examples. Be sure to close the root terminal after the installation completes. +==== + +== Installing Ruby + +From terminal, run the following command to install Ruby: + +---- +$ sudo apt-get install ruby-full +---- + +Run the following command to verify that Ruby has installed correctly: +---- +$ ruby -e 'puts "Welcome to Ruby"' +---- +Welcome to Ruby + + + +== Installing RubyGems + +Run the following command to install RubyGems: +---- +$ sudo apt-get install rubygems +---- + +== Installing Git + +Run the following command to install Git version control: +---- +$ sudo apt-get install git-core +---- + +After installation completes, run the following command to verify that Git has installed correctly: +---- +$ git --version +---- + +This command returns the Git version number that was installed. + +== Installing Client Tools + + +When the required software has been successfully installed, run the following command to install the client tools: +---- +$ sudo gem install rhc +---- + +== Installation Issues and Tips + +*Executing Client Tool Commands from Any Directory* + +On Ubuntu and other Debian based distributions, the client tools by default are stored in the */var/lib/gems/1.8/bin* directory. Therefore, all client tool commands must be executed from this directory, and you must append *./* to each command. + + +However, this behavior can be changed by adding the client tools to the PATH environment variable so that you can run client tool commands from any directory. Run the following command to add the client tools to the PATH environment variable, and make it persistent for an entire terminal session: +---- +$ sudo export PATH=/var/lib/gems/1.8/bin:$PATH +---- +Now you can run client tool commands from any directory in the current Terminal session. Note that you must do this each time you close the current Terminal session and start a new one. + +For a more permanent solution, add the *export PATH=/var/lib/gems/1.8/bin:$PATH* command to your *_.bashrc_* file. Therefore, each time a new Terminal session is started, the client tools are automatically added to the PATH environment variable. You can then run all client tool commands from any directory in Terminal. + + +*Making Client Tools Available to All Users* + +Initially the OpenShift Online client tools are only available to the user installed them. Run the following command to make the client tools available for all users on an Ubuntu system: +---- +$ sudo ln -s /var/lib/gems/1.8/bin/rhc* /usr/bin/ +---- + +This creates a symbolic link to the client tools binaries in the default search path, and make the client tools available to all users on that system. + +//When the installation completes, proceed to <> to configure the client tools using the interactive setup wizard. diff --git a/client_tools_install_guide/installing_client_tools_on_windows.adoc b/client_tools_install_guide/installing_client_tools_on_windows.adoc new file mode 100644 index 000000000000..2a8787570e56 --- /dev/null +++ b/client_tools_install_guide/installing_client_tools_on_windows.adoc @@ -0,0 +1,77 @@ +[[Installing_Client_Tools_on_Windows]] += Installing Client Tools on Windows + +:icons: + +The OpenShift Client Tools are supported on the following Windows operating systems: + +* Windows 7 +* Windows Vista +* Windows XP +* Windows 2000 + +[NOTE] +==== +Sufficient privileges are required to install software on Windows systems. Depending on specific user permissions, disabling the User Account Control (UAC) on Windows Vista or Windows 7 operating systems may be necessary. +==== + +//=== Before you begin + +Installing the client tools on Windows operating system comprises three steps: + + +*Step 1*: Install Ruby Installer + +*Step 2*: Install Git version control + +*Step 3*: Install the client tools + +Before you can install the client tools, you must download and install *_RubyInstaller_* and *_Git_* on your system. + +=== Install RubyInstaller + +1. From link:$$http://rubyinstaller.org/$$[rubyinstaller.org], download and save the latest RubyInstaller package for Windows to your desired directory. +//+ +//[[img-rubyinstaller]] +//image::/home/Bilhar/Documents/AsciiDoc_Migration/Client_Tools_Install_Guide/images/2830.png[] + +2. Double-click the executable RubyInstaller file downloaded in the previos step to launch the RubyInstaller installation wizard. Accept the _Ruby License Agreement_ and click btn:[OK]. + +3. Select the _Add Ruby executables to your PATH_ check box, and click btn:[Install] to begin the installation. ++ +.Select PATH +image::/home/Bilhar/Documents/AsciiDoc_Migration/Client_Tools_Install_Guide/images/2829.png[] ++ +Click *Finish* when the install completes. + +=== Install Git Version Control + +1. From link:$$http://msysgit.github.com/$$[http://msysgit.github.com/], download and save the latest version of Git for Windows to your desired directory. + +2. Double-click the executable Git file downloaded in the previous step to launch the Git installation wizard. Click btn:[Next] until you are prompted to adjust the PATH environment. + +3. Select the *Run Git and included UNIX tools from the Windows Command Prompt* check box and click btn:[Next]. This is so that you can use the default Windows command prompt for Git and SSH operations. ++ +.Select Git PATH +image::/home/Bilhar/Documents/AsciiDoc_Migration/Client_Tools_Install_Guide/images/3265.png[] + +4. Select the Checkout Windows-style, commit Unix-style line endings check box, and click btn:[Next]. ++ +.Select Line Editing +image::/home/Bilhar/Documents/AsciiDoc_Migration/Client_Tools_Install_Guide/images/2828.png[] ++ +Click btn:[Finish] when the install completes. + +=== Install the Client Tools + +1. Open Windows Command Prompt. + +a. Click btn:[Start], type *cmd* in the *Start Search* text box, and then click btn:[cmd]. + +2. From the *cmd* prompt, install the client tools: ++ +---- +$ gem install rhc +---- + +//When the installation completes, proceed to <> to configure the client tools using the interactive setup wizard. \ No newline at end of file diff --git a/client_tools_install_guide/updating_client_tools.adoc b/client_tools_install_guide/updating_client_tools.adoc new file mode 100644 index 000000000000..92924861e889 --- /dev/null +++ b/client_tools_install_guide/updating_client_tools.adoc @@ -0,0 +1,14 @@ +[[Updating_Client_Tools]] += Updating Client Tools + +If you installed the client tools gem, run the following command to update the client tools: + +---- +$ gem update rhc +---- + +Alternatively, if you installed the the client tools with +yum+, run the following command to update the client tools, and replace _packagename_ with rubygem-rhc for Fedora or rhc for Red Hat Enterprise Linux: +---- + +$ yum update packagename +---- \ No newline at end of file