NodeJS is a server runtime for JavaScript. Many newer apps and services find that the asynchronous, single-process approach espoused by Node is easier to reason about and scale. While PHP still remains a popular choice for distributing commodity web apps, Node is becoming a big contender for uses more complicated than the average blog or wiki engine. Here we’ll get Node up and running on CentOS 7. We’ll also set up a simple app to demonstrate how you’d go about running any other Node-based code.<\/p>\n
Confirm that you have the following before you follow this guide: You can run Node-based applications as root, but any compromise will give an attacker the ability to run code and perform actions that affect the entire server. For best results, each Node-based app should run under a dedicated user account.<\/p>\n Start by updating your server to ensure that it has all available security patches and bugfixes. Perform the update step regularly to keep your system secure and performant. We’ll also install packages that Node expects your server to have.<\/p>\n There are a few ways you might install the Node runtime. The first method involves using a Yum repository.<\/p>\n There are a few different versions of Node. Which you install will depend upon the requirements of the code you are attempting to run, or in some instances, on your environment’s ability to upgrade and run new versions of Node.<\/p>\n If you need stability above all else, and can’t easily upgrade components, stick with the Node Long-Term Support (LTS) release. This is currently V4.x. Here is how you’d enable and install Node’s LTS release via Yum:<\/p>\n Node V5 is a more recent version with additional features and APIs. Here is how Node V5 is installed via Yum:<\/p>\n Node V6 will eventually become the new LTS release. V6’s biggest feature is significant compatibility with Ecmascript 2015, new functionality that vastly improves and simplifies the JavaScript language.<\/p>\n Finally, V0.10 is an older version of Node required by some older apps and frameworks. In general, don’t use this repository unless you know that you need it.<\/p>\n If all of this seems complicated, you can just install the latest stable version of Node as shipped by CentOS. If you don’t know which version to use, try this method to get a Node runtime that will almost certainly work for you.<\/p>\n Another way to install Node is via the Node Version Manager. NVM can install several versions of Node concurrently, switching between them as required. Use this method only if you are familiar with Node, or if you are comfortable administering servers and installing language runtimes without package repositories.<\/p>\n Start by installing NVM’s dependencies.<\/p>\n Next you’ll need the NVM installation script available on GitHub:<\/p>\n When you’ve finished the installation, you’ll need to log out and in again so the modifications it made to your startup shell scripts take effect.<\/p>\n Use NVM to list all available versions of NodeJS, then select the one you wish to install.<\/p>\n You’ll see many versions. At the time of writing, the latest version of Node is 6.2.2. Use this version, or whatever the latest version NVM lists, unless you specifically need an earlier release.<\/p>\n Use this command to install the version you choose to run:<\/p>\n To ensure that the installation worked, let’s have NVM list the Node versions it has installed. You should see the version you chose earlier.<\/p>\n You’ve installed a version of Node, but since NVM can install several versions at the same time, you must pick which is currently active. Here we’ll activate the release you’ve just downloaded.<\/p>\n Now we verify that the activation worked.<\/p>\n Node is now installed. To ensure that it works, we’ll deploy a simple web server that displays a message when accessed. The application will use the popular Express web framework.<\/p>\n First, create a directory that will contain the application.<\/p>\n Next, create the script that will run the server.<\/p>\n The script should contain this code:<\/p>\n Save and exit. Next we need to install the Express framework so your script can use it.<\/p>\n Run the script you’ve just created.<\/p>\n You’ll see a message on the console confirming that the server is listening for incoming connections.<\/p>\n Visit the URL for the server you just created. If you see the message “Globo.Tech says Hello!” in your browser, your Node stack is correctly set up!<\/p>\n You can now run any number of modern Node apps on this server. Share this article with anyone who might be looking for a great platform on which to develop modern, internet-facing services.<\/p>\n If found this guide helpful, please be sure to share it with friends. You can also take a look at our other guides where we cover topics such as networking, databases, and server applications.<\/p>\n","protected":false},"excerpt":{"rendered":" How to install NodeJS and run node applications on CentOS 7 NodeJS is a server runtime for JavaScript. Many newer apps and services find that the asynchronous, single-process approach espoused by Node is easier to reason about and scale. While PHP still remains a popular choice for distributing commodity web apps, Node is becoming a<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[71],"tags":[],"class_list":["post-2528","post","type-post","status-publish","format-standard","hentry","category-applications","operating_system-centos-7"],"yoast_head":"\n
\n\u2022 1 Node (Cloud Server<\/b><\/a> or Dedicated Server<\/b><\/a>) running CentOS 7.
\n\u2022 Root access to the node.<\/p>\nTutorial<\/h2>\n
yum update
\nyum install gcc-c++ make<\/code><\/p>\ncurl --silent --location https:\/\/rpm.nodesource.com\/setup_4.x | bash -<\/code><\/p>\ncurl --silent --location https:\/\/rpm.nodesource.com\/setup_5.x | bash -<\/code><\/p>\ncurl --silent --location https:\/\/rpm.nodesource.com\/setup_6.x | bash -<\/code><\/p>\ncurl --silent --location https:\/\/rpm.nodesource.com\/setup | bash -<\/code><\/p>\nyum install nodejs<\/code><\/p>\nyum groupinstall 'Development Tools'
\nyum install wget<\/code><\/p>\ncd \/root
\nwget https:\/\/raw.githubusercontent.com\/creationix\/nvm\/v0.31.2\/install.sh
\nbash install.sh<\/code><\/p>\nnvm ls-remote<\/code><\/p>\n(....)
\nv4.4.2
\nv4.4.3
\nv4.4.4
\nv4.4.5
\nv4.4.6
\nv4.4.7
\nv5.0.0
\nv5.1.0
\nv5.1.1
\nv5.2.0
\nv5.3.0
\nv5.4.0
\nv5.4.1
\nv5.5.0
\nv5.6.0
\nv5.7.0
\nv5.7.1
\nv5.8.0
\nv5.9.0
\nv5.9.1
\nv5.10.0
\nv5.10.1
\nv5.11.0
\nv5.11.1
\nv5.12.0
\nv6.0.0
\nv6.1.0
\nv6.2.0
\nv6.2.1
\nv6.2.2<\/code><\/p>\nnvm install 6.2.2<\/code><\/p>\nnvm ls<\/code>
\n-> v6.2.2
\ndefault -> 6.2.2 (-> v6.2.2)
\nnode -> stable (-> v6.2.2) (default)
\nstable -> 6.2 (-> v6.2.2) (default)
\niojs -> N\/A (default)<\/code><\/p>\nnvm use 6.2.2<\/code><\/p>\nroot@nodejs:~# node -v
\nv6.2.2<\/code><\/p>\nmkdir \/home\/nodeapp
\ncd \/home\/nodeapp<\/code><\/p>\nnano nodetest.js<\/code><\/p>\n!\/usr\/bin\/env node
\nvar express = require('express');
\nvar app = express();
\napp.get('\/', function (req, res) {
\n res.send('Globo.Tech says Hello!');
\n});
\napp.listen(6915, function () {
\n console.log('Basic NodeJS app listening on port 6915.');
\n});<\/code><\/p>\nnpm install express<\/code><\/p>\nnode \/home\/nodeapp\/nodetest.js<\/code><\/p>\nnode nodetest.js
\nBasic NodeJS app listening on port 6915.<\/code><\/p>\nGiven that we have setup an environment path in the beginning of our script, we can make it executable to run it without specifying \"node\" in front of the script.
\nchmod +x \/rhome\/nodeapp\/nodetest.js
\n.\/nodetest.js<\/code><\/p>\nConclusion<\/h2>\n