Skip to content

Latest commit

 

History

History
264 lines (182 loc) · 12 KB

get-started-scl-rhel6-nodejs.adoc

File metadata and controls

264 lines (182 loc) · 12 KB

Path Intro section

Get started developing with Node.js from Red Hat Software Collections in under 10 minutes.

Prerequisites section title

Introduction and Prerequisites

Prerequisites section

In this tutorial, you will set your system up to install software from Red Hat Software Collections (RHSCL), which provides the latest development technologies for Red Hat Enterprise Linux. Then, you will install Node.js and run a simple “Hello, World” application. The whole tutorial should take less than 10 minutes to complete.

You will need a Red Hat Enterprise Linux 6 system with a current Red Hat subscription that allows you to download software and updates from Red Hat. Access to the Red Hat Software Collections (RHSCL) is included with many Red Hat Enterprise Linux (RHEL) subscriptions. For more information about which subscriptions include RHSCL, see How to use Red Hat Software Collections (RHSCL) or Red Hat Developer Toolset (DTS

If you don’t have a Red Hat Enterprise Linux subscription, you can try it for free. Get started with an evaluation at https://access.redhat.com/products/red-hat-enterprise-linux/evaluation. Select the Red Hat Enterprise Linux Developer Workstation option to ensure your evaluation will include both RHSCL and DTS.

If you encounter difficulties at any point, see Troubleshooting and FAQ.

Step1 Duration

2 minutes

Step1 Title

Enable Red Hat Software Collections (RHSCL)

Step2 Duration

2 minutes

Step2 Title

Setup your development environment

Step3 Duration

2 minutes

Step3 Title

Hello World and your first application

Step1 Content

In this step you will configure your system to obtain software, including the latest dynamic languages, from the RHSCL software repository. Instructions are provided for both the command line (CLI) and graphical user interface (GUI).

Note: If your system uses Red Hat Network (RHN) Classic instead of Red Hat Subscription Management (RHSM) for managing subscriptions and entitlements, please skip this step and follow the Installation chapter of the Red Hat Software Collections 2.0 Release Notes. The instructions in this section are only for systems using RHSM. The remainder of this tutorial applies to systems running either RHSM or RHN Classic.

Using the Red Hat Subscription Manager GUI

Red Hat Subscription Manager can be started from the SystemAdministration subgroup of the Applications menu. Alternatively, you can start it from the command prompt by typing subscription-manager-gui.

Select Repositories from the System menu of the subscription manager. In the list of repositories, check the Enabled column for rhel-server-rhscl-6-rpms and rhel-6-server-optional-rpms. If you are using a desktop version of Red Hat Enterprise Linux, the repositories will be named rhel-desktop-rhscl-6-rpms and rhel-6-desktop-optional-rpms.

If you don’t see any RHSCL repositories in the list, your subscription might not include it.

Manage Repositories

See Troubleshooting and FAQ for more information.

Using subscription-manager from the command line

You can add or remove software repositories from the command line using the subscription-manager tool as the root user. Use the --list option to view the available software repositories and verify that you have access to RHSCL:

$ su -
# subscription-manager repos --list | egrep rhscl

If you don’t see any RHSCL repositories in the list, your subscription might not include it. See Troubleshooting and FAQ for more information.

If you are using a desktop edition of Red Hat Enterprise Linux, change -server- to -desktop- in the following commands:

# subscription-manager repos --enable rhel-server-rhscl-6-rpms
# subscription-manager repos --enable rhel-6-server-optional-rpms

Step2 Content

In this next step you will install Node.js 0.10 from RHSCL:

$ su -
# yum install nodejs010

Note: The V8 JavaScript runtime is installed automatically as a dependency.

If you need help, see Troubleshooting and FAQ.

Step3 Content

Under your normal user ID, start a Terminal window. First, use scl enable to add Node.js to your environment, then start node to check the version.

$ scl enable nodejs010 bash
$ node --version
v0.10.35

The next step is to create a JavaScript program that can be run from the command line. Using your preferred text editor, create a file named hello.js:

$ nano hello.js

Add the following text to the file:

console.log("Hello, Red Hat Developers World!")

Save it and exit the editor. Run it with the node command:

$ node ./hello.js
Hello, Red Hat Developers World

If you get the error: node command not found, you need to run scl enable nodejs010 bash first.

The next step is to try a slightly larger Node.js example that implements a tiny web server. Using your preferred text editor, create a file named hello-http.js:

$ nano hello-http.js

Add the following text to the file:

var http = require('http');
http.createServer(function (req, res) {
    res.writeHead(200, {'Content-Type': 'text/plain'});
    res.end('Hello, Red Hat Developers World!\n');
}).listen(8000, '127.0.0.1');
console.log('Server running at http://127.0.0.1:8000/');

Save it and exit the editor. Run it with the node command:

$ node ./hello-http.js

Now use Firefox or your preferred browser to connect to the Node.js web server http://localhost:8000/.

Working with RHSCL packages

The software packages in RHSCL are designed to allow multiple versions of software to be installed concurrently. To accomplish this, the desired package is added to your runtime environment as needed with the scl enable command. When scl enable runs, it modifies environment variables and then runs the specified command. The environmental changes only affect the command that is run by scl and any processes that are run from that command. The steps in this tutorial run the command bash to start a new interactive shell to work in the updated environment. The changes aren’t permanent. Typing exit will return to the original shell with the original environment. Each time you login, or start a new terminal sesssion, scl enable needs to be run again.

While it is possible to change the system profile to make RHSCL packages part of the system’s global environment, this is not recommended. Doing this can cause conflicts and unexpected problems with other applications because the system version of the package is obscured by having the RHSCL version in the path first.

Permanently enable RHSCL in your development environment

To make one or more RHSCL packages a permanent part of your development environment, you can add it to the login script for your specific user ID. this is the recommend approach for development as only processes run under your user ID will be affected.

Using your preferred text editor, add the following line to ~/.bashrc:

source scl_source enable nodejs010

After making the change, you should log out and log back in again.

When you deliver an application that uses RHSCL packages, a best practice is to have your startup script handle the scl enable step for your application. You should not ask your users to change their environment as this is likely to create conflicts with other applications.

Where to go next?

Learn Node.js and JavaScript using NodeSchool.io tutorials

Now that you have Node.js installed, use the tutorials from nodeschool.io to learn Node.js and JavaScript. You need to have already run scl enable nodejs010 bash or have added Node.js permanently to your development environment.

Install the JavaScript and Node.js tutorials into your current directory:

$ npm install javascripting
$ npm install learnyounode

Temporarily add node_modules/.bin to your PATH:

$ export PATH=$PATH:$PWD/node_modules/.bin

Run the JavaScript tutorial:

$ javascripting

Run the Node.js tutorial:

$ learnyounode

View documentation on the Nodejs.org web site
http://nodejs.org/documentation/

Find additional RHSCL Node.js modules
$ yum list available nodejs\*

View the list of software available in RHSCL
$ yum --disablerepo="*" --enablerepo="rhel-server-rhscl-6-rpms" list available

More Resources

Become a Red Hat developer: developers.redhat.com

Red Hat delivers the resources and ecosystem of experts to help you be more productive and build great solutions. Register for free at developers.redhat.com.

Faq section title

Troubleshooting and FAQ

Faq section

  1. The RHSCL repository is not available or is not found on my system.

    The name of the repository depends on whether you have a server or desktop version of Red Hat Enterprise Linux installed.

    Some Red Hat Enterprise Linux subscriptions do not include access to RHSCL. See How to use Red Hat Software Collections (RHSCL) or Red Hat Developer Toolset (DTS).

    You can use subscription --list to view the available software repositories and verify that you have access to RHSCL:

    $ su -
    # subscription-manager repos --list | egrep rhscl
  2. yum install fails due to a missing dependency.

    These packages are in the optional RPMs repository, which is not enabled by default. See [Enable Red Hat Software Collections] for how to enable both the optional RPMs and RHSCL repositories.

  3. How can I find out what RHSCL packages are installed?

    scl --list will show the list of RHSCL packages that have been installed, whether they are enabled or not.

    $ scl --list
    nodejs010
    v8314
  4. How do I find out if there is a newer version of Node.js in the RHSCL?

    How do I find out what version of Node.js is available in the current RHSCL?

    I have the RHSCL repository enabled, but I can’t find the Node.js version listed in this tutorial.

    Use the following command to find packages with matching names:

    # yum list available nodejs\*

  5. I’ve installed Node.js from RHSCL, but node is not in my path.

    I can’t find the node command.

    RHSCL does not alter the system path. You need to use scl enable to change the environment for your session:

    $ scl enable nodejs010 bash

    For more information see the Red Hat Software Collection 2.0 Documentation.

  6. When I try to run node, I get an error about a missing shared library.

    This is due to not having run scl enable first. When scl enable runs, in addition to setting up the command search PATH, it also sets up the search path for shared libraries, LD_LIBRARY_PATH.