Shulou(Shulou.com)06/01 Report--

This article mainly introduces the relevant knowledge of node.js instance deployment analysis, the content is detailed and easy to understand, easy to operate, and has a certain reference value. I believe you will gain something after reading this article on node.js instance deployment analysis. Let's take a look at it.

Server

The server chose: 9.92 one month, suitable for personal development and testing.

Configuration:

System: centos6.5 64-bit (a type of linux system)

Configure environment configure server environment

1. Start the CVM instance in the Ali Cloud management console

two。 Log in to the server: use putty or xshell (I use xshell):

After downloading and installing xsheel, create a new session.

3. Update yum to the latest version:

Yum-y update

4. We will build node.js with the latest source code, and to install the software, we need a set of development tools to compile the source code:

Yum-y groupinstall "development tools"

Install node.js

1. To start installing node.js, go to the / usr/src folder, which is usually used to store the software source code:

two。 To get the source code of the zip file from the node.js site, the version I chose is v0.10.18:

Wget http://nodejs.org/dist/v0.10.18/node-v0.10.18.tar.gz

3. Extract the source file and enter it into the compressed folder:

Tar zxf node-v0.10.18.tar.gz cd node-v0.10.18

4. Execute the configuration script for compilation preprocessing:

. / configure

5. Start compiling source code

Make

6. When the compilation is complete, we need to make it available system-wide, the compiled binaries will be placed in the system path, and by default, the node binaries should be placed under the / user/local/bin/node folder:

Make install

7. Now that node.js is installed, you are ready to deploy the application, starting by installing express middleware and forever (a very useful module to ensure that the application starts and restarts if needed) using node.js 's module manager npm:

Npm-g install express forever

8. Set up a hyperlink, otherwise you will report "command not found" when you sudo node

Sudo ln-s / usr/local/bin/node / usr/bin/node sudo ln-s / usr/local/lib/node / usr/lib/node sudo ln-s / usr/local/bin/npm / usr/bin/npm sudo ln-s / usr/local/bin/node-waf / usr/bin/node-waf sudo ln-s / usr/local/bin/forever / usr/bin/forever

Install mongodb (the database used in the project)

1. Installation instructions:

System environment: centos-6.5

Installation software: mongodb-linux-x86_64-2.4.9.tgz

Download address:

Upload location: / usr/local/

Software installation location: / usr/local/mongodb

Data storage location: / var/mongodb/data

Log location: / var/mongodb/logs

two。 Go to the folder / usr/local and download the mongodb source code:

Cd / usr/localwget http://fastdl.mongodb.org/linux/mongodb-linux-x86_64-2.4.9.tgz

3. Extract the installation package and rename the folder to mongodb

Tar zxvf mongodb-linux-x86_64-2.4.9.tgz mv mongodb-linux-x86_64-2.4.9 mongodb

4. Create a mongodb folder in the var folder, and create a folder data to store data, and logs to store logs

Mkdir / var/mongodbmkdir / var/mongodb/datamkdir / var/mongodb/logs

5. Open the rc.local file and add the centos boot entry:

Vim / etc/rc.d/rc.local

6. Append the mongodb startup command to this file to allow mongodb to boot itself:

The copy code is as follows:

/ usr/local/mongodb/bin/mongod-dbpath=/var/mongodb/data-logpath / var/mongodb/logs/log.log-fork

7. Start mongodb

The copy code is as follows:

/ usr/local/mongodb/bin/mongod-dbpath=/var/mongodb/data-logpath / var/mongodb/logs/log.log-fork

8. You can see the following message indicating that the installation has completed and started successfully:

Forked process: 18394all output going to: / var/mongodb/logs/log.log

Upload code

You can consider using ftp (xftp, sftp, etc.), svn, git to upload the code. I use xftp.

After downloading and installing xftp, start xftp and create a new session:

I uploaded the code to the / home directory folder.

Start the application

1. Enter the directory where the code is stored and store it in the / home/app directory. Server.js is the program entry file.

Cd / home/appsudo forever start server.js

two。 View running applications:

Sudo forever list

3. If you need to close the application, the command is as follows:

Sudo forever stop 0

Since then, if there is no accident, the project has been deployed successfully.

This is the end of the article on "node.js instance deployment Analysis". Thank you for reading! I believe you all have a certain understanding of the knowledge of "node.js instance deployment Analysis". If you want to learn more, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.