This document provides steps for deploying a Node.js application without getting fired, from initial setup through scaling. It begins with installing Node.js on a VPS or virtual private server. Basic steps include initializing version control with Git, adding logging and error handling, and using Upstart to ensure the app runs at boot and respawns if it crashes. Advanced techniques include using multiple processes, a cache like Varnish, staging environments, and eventually multiple app servers with the database on separate boxes controlled by tools like node-control. The document emphasizes automating deployments and scaling gradually over time.

1. HOW TO DEPLOY NODE
without getting fired

2. @seanhess
seanhess.github.com

4. Try it yourself
deploynode.tk
user public
pass public
ssh public@deploynode.tk

5. WHO
ARE
YOU?

6. from FIRST STEPS
to MISSTEPS
toSCALE

7. Ratinatorly
who RATES the RATE-MEN?

8. SALARY is for chumps
100,000
shares of sweat-equity

9. you decide to try

10. Your First Node
“but my brother says
that .NET is the best
language”

11. 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")

12. your app is a
LONG RUNNING
PROCESS
it handles all the requests
...if it’s on

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

14. SHARED HOSTING FAIL *
you need to run a
PROGRAM

15. VPS WIN!
like a cheap
DEDICATED SERVER

16. sudo make me a server
okay...

21. > ssh root@ratinator.ly
root@ratinatorly's 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

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

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

24. your
app BELONGS
to your
ssh session
LOG OUT == DIE

25. SCREEN you
keeps
LOGGED IN

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

27. let’s add
VERSION CONTROL
use GIT to deploy

28. manage your
DEPENDENCIES
package.json
> npm install

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

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

31. port 80
• must run as root

32. This is where I stop trying
to design my slides

33. It keeps DYING!
“Maybe we should try
windows servers instead”

34. upstart
• OS will start on boot
• Respawn

35. monitoring
• know if it goes down

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

37. logging
• keep your output

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

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

40. complicated deploy
• it can get easy to miss a step

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

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

43. Multiple Processes
• cluster up to your cores

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

45. Staging Box

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

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

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

49. automate
rem
em
with
erb
UPSTARTand GIT
or CHEATwith
HEROKU

50. seanhess.github.com
@seanhess

51. > npm install express
...
> ls
app.js node_modules
> node app.js
Listening on 3333