How to deploy node to production

HOW TO DEPLOY NODEwithout getting fired

@seanhessseanhess.github.com

Try it yourself deploynode.tk user public pass publicssh public@deploynode.tk

WHO AREYOU?

from FIRST STEPS to MISSTEPS toSCALE

Ratinatorlywho RATES the RATE-MEN?

SALARY is for chumps100,000shares of sweat-equity

you decide to try

Your First Node“but my brother saysthat .NET is the best language”

var express = require(express)var app = express.createServer()app.get(/, function(req, res) { res.send("Hello World!")})app.listen(3333)console.log("Listening on 3333")

your app is aLONG RUNNINGPROCESSit handles all the requests ...if it’s on

the PROTOTYPE ONLINE must be“Sequoia is going to LOVE this”

SHARED HOSTING FAIL *you need to run a PROGRAM

VPS WIN! like a cheapDEDICATED SERVER

sudo make me a server okay...

> ssh root@ratinator.lyroot@ratinatorlys password:Welcome to Ubuntu 11.04 (GNU/Linux# adduser node# adduser node sudo# sudo apt-get install python-software-properties# sudo apt-add-repository ppa:chris-lea/node.js# sudo apt-get update# sudo apt-get install nodejs npm

MAKE IT GO•copy our code• node app.js

DON’T CLOSE the LID!!“I didn’t do anything... Check Energy Saver”

your app BELONGS to your ssh sessionLOG OUT == DIE

SCREEN you keeps LOGGED IN

Undo! Rollback!“I know enough HTML to be dangerous”

let’s addVERSION CONTROL use GIT to deploy

manage yourDEPENDENCIES package.json > npm install

a PROCESS emerges• git commit and push• log in to server• pull• npm install• restart

LAUNCH!“I’ve got Techcrunch right where I want them”

port 80• must run as root

This is where I stop trying to design my slides

It keeps DYING! “Maybe we should trywindows servers instead”

upstart• OS will start on boot• Respawn

monitoring• know if it goes down

It works for me!or, when the cracks first began to show...

logging• keep your output

uncaughtExceptionprocess.on(“uncaughtException”, function(err) { console.log(err.message)})

Don’t forget step 6!“Will you put my changes up for me?”

complicated deploy• it can get easy to miss a step

automated• keep the knowledge in your code base• put extra stuff in package.json “install”

Too Slow!“Let’s just throw more money at this"

Multiple Processes• cluster up to your cores

Varnish Cache • avoid repeating work • set headers and gosudo apt-get install varnishsudo vim /etc/default/varnish # port 80sudo vim /etc/varnish/default.vcl # point to our app at port 3333sudo /etc/init.d/varnish start

Staging Box

cheat with Heroku• it’s easy, but can be expensive

Scale“We should aim for... 100 million users”

Multiple Servers• more app servers• varnish and db on separate box• use node-control to deploy• smart db = good for a long time

automate rem emwith erb UPSTARTand GITor CHEATwith HEROKU

seanhess.github.com @seanhess

> npm install express...> lsapp.js node_modules> node app.jsListening on 3333

How to deploy node to production

by Sean Hess

Accessibility

Categories

Upload Details

Usage Rights

Statistics

How to deploy node to production Presentation Transcript