Download as PDF, PPTX
Uploaded bySean Hess
How to deploy node to production
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.
How to deploy node to production
- 1. HOW TO DEPLOYNODE without getting fired
- 2.
- 4. Try it yourself deploynode.tk user public pass public ssh public@deploynode.tk
- 5.
- 6. from FIRST STEPS to MISSTEPS toSCALE
- 7. Ratinatorly who RATES theRATE-MEN?
- 8. SALARY is forchumps 100,000 shares of sweat-equity
- 9.
- 10. Your First Node “butmy 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 isa 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 mea server okay...
- 21. > ssh root@ratinator.ly root@ratinatorly'spassword: 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 •copyour 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 knowenough 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 Techcrunchright where I want them”
- 31. port 80 • must run as root
- 32. This is whereI 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 forme! 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 step6! “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 justthrow 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.
- 46. cheat with Heroku • it’s easy, but can be expensive
- 47. Scale “We should aimfor... 100 million users”
- 48. Multiple Servers • moreapp 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 installexpress ... > ls app.js node_modules > node app.js Listening on 3333
Editor's Notes
- #2 quick intro to topic\n
- #3 long-time consultant\nCofounder of i.TV\n
- #4 make TV amazing. \ncool announcements\nused node in production for 2 years. STORY. We picked it because we thought it was cool.\n\n
- #5 this is going to be a walk-through\ninterrupt me\n
- #6 front-end developers?\ngotten a node app working on your computer?\ndeployed a node or ruby app to production by hand before?\n\n
- #7 WALKTHROUGH. \nfollow a company. some of the steps are wrong, but we will explain why and show how to correct them.\nWe’re going to follow the story of a budding young entreprenuer\nBegin the story: local js meetup. talk on semicolons\n\n
- #8 \n
- #9 \n
- #10 because you know and like javascript, and you heard it scales\nDOES have a big advantage: JS Skills\n
- #11 All the real companies use .NET\nAfter a 3 hour meeting with your partner, you finally convince him to leave the decision to you and head out to learn. \n
- #12 \n
- #13 you don’t make a new one each time a requests. Only will work if it’s on and plugged in, ready to go. Listens on a socket. Different than PHP.\nIf we Control-C the program stops. \n
- #14 \n
- #15 * we’ll show off some cool stuff later\n
- #16 nice thing is they are all the same, so you can jump between providers depending on cost\n
- #17 domain name? (hosts file)\nSet up the server, and show how to log in. \nSwitch to VM?\n\n
- #18 \n
- #19 \n
- #20 \n
- #21 \n
- #22 Add a non-root user\ninstall nodejs (source: google)\n
- #23 Add a non-root user\ninstall nodejs (source: google)\n
- #24 Add a non-root user\ninstall nodejs (source: google)\n
- #25 Add a non-root user\ninstall nodejs (source: google)\n
- #26 Add a non-root user\ninstall nodejs (source: google)\n
- #27 Add a non-root user\ninstall nodejs (source: google)\n
- #28 Add a non-root user\ninstall nodejs (source: google)\n
- #29 Add a non-root user\ninstall nodejs (source: google)\n
- #30 Add a non-root user\ninstall nodejs (source: google)\n
- #31 Add a non-root user\ninstall nodejs (source: google)\n
- #32 Add a non-root user\ninstall nodejs (source: google)\n
- #33 Add a non-root user\ninstall nodejs (source: google)\n
- #34 Add a non-root user\ninstall nodejs (source: google)\n
- #35 Add a non-root user\ninstall nodejs (source: google)\n
- #36 get it running online\n
- #37 \n
- #38 demo it!\neven if you run it in the background\n
- #39 DEMO!\n
- #40 The “boss” makes you tell him how to edit the app. He breaks it. \n
- #41 Demo using git to deploy. (checkout, public)\ngit clone git://github.com/seanhess/ratinatorly.git\n
- #42 intro to npm\nshow how to deploy without copying node_modules\nuse npm init\nexpress: \n
- #43 \n
- #44 \n
- #45 \n
- #46 tell the story\n
- #47 \n
- #48 DEMO init script\nDEMO deploying with init script\n
- #49 montastic.com\n
- #50 when it crashes\nuncaught exception\nlogs\n
- #51 DEMO redirect with upstart\nDEMO track down the bug\nCan add fancy log analysis later\n
- #52 DEMO: show the uncaughtException code\n
- #53 \n
- #54 \n
- #55 DEMO: bash automated deploy\nNOPASSWD in sudoers (sudo visudo)\nsave fancier stuff for later when you have multiple servers (node-control, capistrano)\n
- #56 \n
- #57 DEMO: paste in the cluster code from the real one and check it closely\n\nvar os = require('os')\nvar cluster = require('cluster')\nif (cluster.isMaster) {\n\n for (var i = 0; i < os.cpus().length; i++) {\n cluster.fork()\n }\n}\nelse {\n app.listen(3333)\n console.log("Listening on 3333")\n}\n\n
- #58 DEMO\nsudo apt-get install varnish\nsudo vim /etc/default/varnish\nsudo vim /etc/varnish/default.vcl\nsudo /etc/init.d/varnish start\n\n
- #59 \n
- #60 heroku create --stack cedar\ngit push heroku master\nchange the port! (check the logs)\n
- #61 \n
- #62 \n
- #63 \n
- #64 \n
- #65 DEMO IT!\n
- #66 DEMO IT!\n
- #67 DEMO IT!\n
- #68 DEMO IT!\n
- #69 DEMO IT!\n
- #70 DEMO IT!\n